Sensor with halo light system

ABSTRACT

A thermostat for a building includes a halo light emitting diode (LED) system including one or more LEDs configured to emit light and a halo diffuser structured around at least a portion of an outer edge of the thermostat. The halo diffuser is configured to diffuse the emitted light of the one or more LEDs around at least the portion of the outer edge of the thermostat. The thermostat includes a processing circuit configured to receive one or more data streams, determine whether the one or more data streams indicate a building emergency condition, and operate the one or more LEDs of the halo LED system to indicate the building emergency condition to a user.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

This application is a Continuation of U.S. application Ser. No.16/246,366, filed Jan. 11, 2019, incorporated herein by reference in itsentirety, which is a Continuation-In-Part of U.S. application Ser. No.15/336,793, filed Oct. 28, 2016, incorporated herein by reference in itsentirety, which claims priority from Provisional Application U.S.Application 62/247,672, filed Oct. 28, 2015, incorporated herein byreference in its entirety and which claims priority from ProvisionalApplication U.S. Application 62/274,750, filed Jan. 4, 2016,incorporated herein by reference in its entirety and which claimspriority from Provisional Application U.S. Application 62/275,199, filedJan. 5, 2016, incorporated herein by reference in its entirety and whichclaims priority from Provisional Application U.S. Application62/275,202, filed Jan. 5, 2016, incorporated herein by reference in itsentirety and which claims priority from Provisional Application U.S.Application 62/275,204, filed Jan. 5, 2016, incorporated herein byreference in its entirety and which claims priority from ProvisionalApplication U.S. Application 62/275,711, filed Jan. 6, 2016,incorporated herein by reference in its entirety and which is aContinuation-In-Part of U.S. application Ser. No. 15/336,792, filed Oct.28, 2016, incorporated herein by reference in its entirety, which claimspriority from Provisional Application U.S. Application 62/247,672, filedOct. 28, 2015, incorporated herein by reference in its entirety andwhich claims priority from Provisional Application U.S. Application62/274,750, filed Jan. 4, 2016, incorporated herein by reference in itsentirety and which claims priority from Provisional Application U.S.Application 62/275,204, filed Jan. 5, 2016, incorporated herein byreference in its entirety and which claims priority from ProvisionalApplication U.S. Application 62/275,202, filed Jan. 5, 2016,incorporated herein by reference in its entirety and which claimspriority from Provisional Application U.S. Application 62/275,199, filedJan. 5, 2016, incorporated herein by reference in its entirety and whichclaims priority from Provisional Application U.S. Application62/275,711, filed Jan. 6, 2016, incorporated herein by reference in itsentirety and which is a Continuation-In-Part of U.S. application Ser.No. 15/338,221, filed Oct. 28, 2016, incorporated herein by reference inits entirety and which is a Continuation-In-Part of U.S. applicationSer. No. 15/336,789, filed Oct. 28, 2016, incorporated herein byreference in its entirety, which claims priority from ProvisionalApplication U.S. Application 62/247,672, filed Oct. 28, 2015,incorporated herein by reference in its entirety and which claimspriority from Provisional Application U.S. Application 62/274,750, filedJan. 4, 2016, incorporated herein by reference in its entirety and whichclaims priority from Provisional Application U.S. Application62/275,202, filed Jan. 5, 2016, incorporated herein by reference in itsentirety and which claims priority from Provisional Application U.S.Application 62/275,199, filed Jan. 5, 2016, incorporated herein byreference in its entirety and which claims priority from ProvisionalApplication U.S. Application 62/275,204, filed Jan. 5, 2016,incorporated herein by reference in its entirety and which claimspriority from Provisional Application U.S. Application 62/275,711, filedJan. 6, 2016, incorporated herein by reference in its entirety and whichis a Continuation-In-Part of U.S. application Ser. No. 15/397,722, filedJan. 3, 2017, incorporated herein by reference in its entirety, whichclaims priority from Provisional Application U.S. Application62/274,750, filed Jan. 4, 2016, incorporated herein by reference in itsentirety and which claims priority from Provisional Application U.S.Application 62/275,204, filed Jan. 5, 2016, incorporated herein byreference in its entirety and which claims priority from ProvisionalApplication U.S. Application 62/275,199, filed Jan. 5, 2016,incorporated herein by reference in its entirety and which claimspriority from Provisional Application U.S. Application 62/275,202, filedJan. 5, 2016, incorporated herein by reference in its entirety and whichclaims priority from Provisional Application U.S. Application62/275,711, filed Jan. 6, 2016, incorporated herein by reference in itsentirety and which is a Continuation-In-Part of U.S. application Ser.No. 15/336,791, filed Oct. 28, 2016, incorporated herein by reference inits entirety, which claims priority from Provisional Application U.S.Application 62/247,672, filed Oct. 28, 2015, incorporated herein byreference in its entirety and which claims priority from ProvisionalApplication U.S. Application 62/274,750, filed Jan. 4, 2016,incorporated herein by reference in its entirety and which claimspriority from Provisional Application U.S. Application 62/275,204, filedJan. 5, 2016, incorporated herein by reference in its entirety and whichclaims priority from Provisional Application U.S. Application62/275,202, filed Jan. 5, 2016, incorporated herein by reference in itsentirety and which claims priority from Provisional Application U.S.Application 62/275,199, filed Jan. 5, 2016, incorporated herein byreference in its entirety and which claims priority from ProvisionalApplication U.S. Application 62/275,711, filed Jan. 6, 2016,incorporated herein by reference in its entirety and which is aContinuation-In-Part of U.S. application Ser. No. 16/030,422, filed Jul.9, 2018, incorporated herein by reference in its entirety, which is aContinuation-In-Part of U.S. application Ser. No. 15/338,215, filed Oct.28, 2016, incorporated herein by reference in its entirety and which isa Continuation-In-Part of U.S. application Ser. No. 15/336,789, filedOct. 28, 2016, incorporated herein by reference in its entirety andwhich is a Continuation-In-Part of U.S. application Ser. No. 15/338,221,filed Oct. 28, 2016, incorporated herein by reference in its entiretyand which is a Continuation-In-Part of U.S. application Ser. No.15/336,792, filed Oct. 28, 2016, incorporated herein by reference in itsentirety and which is a Continuation-In-Part of U.S. application Ser.No. 15/397,722, filed Jan. 3, 2017, incorporated herein by reference inits entirety and which claims priority from Provisional Application U.S.Application 62/783,580, filed Dec. 21, 2018, incorporated herein byreference in its entirety.

BACKGROUND

The present invention relates generally to thermostats and moreparticularly to the improved control of a building or space's heating,ventilating, and air conditioning (HVAC) system through the use of amulti-function thermostat.

A thermostat is, in general, a component of an HVAC control system.Traditional thermostats sense the temperature of a system and controlcomponents of the HVAC in order to maintain a setpoint. A thermostat maybe designed to control a heating or cooling system or an airconditioner. Thermostats are manufactured in many ways, and use avariety of sensors to measure temperature and other desired parametersof a system.

Conventional thermostats are configured for one-way communication toconnected components, and to control HVAC systems by turning on or offcertain components or by regulating flow. Each thermostat may include atemperature sensor and a user interface. The user interface typicallyincludes a display for presenting information to a user and one or moreuser interface elements for receiving input from a user. To control thetemperature of a building or space, a user adjusts the setpoint via thethermostat's user interface.

SUMMARY

One implementation of the present disclosure is a thermostat for abuilding. The thermostat includes a halo light emitting diode (LED)system including one or more LEDs configured to emit light and a halodiffuser structured around at least a portion of an outer edge of thethermostat. The halo diffuser is configured to diffuse the emitted lightof the one or more LEDs around at least the portion of the outer edge ofthe thermostat. The thermostat includes a processing circuit configuredto receive one or more data streams, determine whether the one or moredata streams indicate a building emergency condition, and operate theone or more LEDs of the halo LED system to indicate the buildingemergency condition to a user.

In some embodiments, the processing circuit is configured to determine athermostat condition that requires user input and operate the one ormore LEDs of the halo LED system to indicate the thermostat condition tothe user.

In some embodiments, the halo LED system further includes one or morewaveguides, each of the one or more waveguides is associated with one ofthe one or more LEDs of the halo LED system. In some embodiments, eachof the one or more waveguides is configured to transmit the lightemitted from one of the one or more LEDs to the halo diffuser. In someembodiments, each of the one or more waveguides is coupled to the halodiffuser at a first end of the one or more waveguides and is proximateone of the one or more LEDs at a second end of the one or morewaveguides.

In some embodiments, the thermostat includes an enclosure including afront portion and a back portion. In some embodiments, the halo diffuseris coupled to the front portion and the back portion and is locatedbetween the front portion and the back portion.

In some embodiments, the processing circuit is configured to operate theone or more LEDs of the halo LED system to indicate the emergencycondition to the user by operating the one or more LEDs in a pattern toindicate one or more emergency response directions to the user promptingthe user to perform a user response to the emergency condition.

In some embodiments, operating the one or more LEDs in the pattern toindicate the one or more emergency response directions comprisesactivating the one or more LEDs sequentially to indicate an emergencynavigation direction.

In some embodiments, the thermostat includes a display screen. In someembodiments, the processing circuit is configured to operate the displayscreen to display one or more emergency response directions in responseto a determination that the one or more data streams indicate theemergency condition.

In some embodiments, the one or more data streams include a buildingdata stream generated by a building management system and a weather datastream generated by a weather server. In some embodiments, thethermostat includes a communication interface configured to receive thebuilding data stream from the building management system via a networkand the weather data stream from the weather server via the network. Insome embodiments, the processing circuit is configured to cause thedisplay screen to display non-emergency information based on thebuilding data stream, determine whether the weather data streamindicates an emergency weather condition, and override the display ofthe non-emergency information by causing the display screen to indicatethe one or more emergency response directions in response to adetermination that the weather data stream indicates the emergencyweather condition.

In some embodiments, the one or more emergency response directionsinclude a building map and one or more evacuation directions, whereinthe one or more evacuation directions include at least one of one ormore directions to a building exit or one or more directions to anemergency shelter in the building. In some embodiments, causing thedisplay screen to display the one or more emergency response directionsincludes causing the display screen to display the building map and theone or more evacuation directions.

In some embodiments, the one or more emergency response directionsinclude an arrow indicating a route through the building for the user tofollow. In some embodiments, causing the display screen to display theone or more emergency response directions includes causing the displayscreen to display the arrow.

In some embodiments, the arrow includes a first portion and an arrowborder surrounding the first portion. In some embodiments, the firstportion is a first color and the arrow border is a second colordifferent than the first color.

Another implementation of the present disclosure is a display device fora building. The display device includes a halo light emitting diode(LED) system including one or more LEDs configured to emit light, a halodiffuser structured around at least a portion of an outer edge of thethermostat, wherein the halo diffuser is configured to diffuse theemitted light of the one or more LEDs around at least the portion of theouter edge of the thermostat, and one or more waveguides, wherein eachof the one or more waveguides is configured to transmit light from oneof the one or more LEDs to the halo diffuser. The display deviceincludes a processing circuit configured to operate the one or more LEDsof the halo LED system to indicate a building emergency condition to auser.

In some embodiments, the processing circuit is configured to receive oneor more data streams, determine whether the one or more data streamsindicate the building emergency condition, and operate the one or moreLEDs of the halo LED system to indicate the building emergency conditionto the user.

In some embodiments, the processing circuit is configured to determine adisplay device condition that requires user input and operate the one ormore LEDs of the halo LED system to indicate the display devicecondition to the user.

In some embodiments, each of the one or more waveguides are coupled tothe halo diffuser at a first end of the one or more waveguides and isproximate to one of the one or more LEDs at a second end of the one ormore waveguides.

In some embodiments, the display device includes an enclosure includinga front portion and a back portion. In some embodiments, the halodiffuser is coupled to the front portion and the back portion and islocated between the front portion and the back portion.

In some embodiments, the processing circuit is configured to operate theone or more LEDs of the halo LED system to indicate the emergencycondition to the user by operating the one or more LEDs in a pattern toindicate one or more emergency response directions to the user promptingthe user to perform a user response to the emergency condition.

In some embodiments, operating the one or more LEDs in the pattern toindicate the one or more emergency response directions comprisesactivating the one or more LEDs sequentially to indicate an emergencynavigation direction.

Another implementation of the present disclosure is a controller for abuilding. The controller includes a halo light system including one ormore lighting components configured to emit light and a halo diffuserstructured around at least a portion of an outer edge of the controller,wherein the halo diffuser is configured to diffuse the emitted light ofthe one or more lighting components around at least the portion of theouter edge of the controller. The controller includes a display deviceconfigured to display information to a user. The controller includes aprocessing circuit configured to receive one or more data streams,determine whether at least one of the one or more data streams indicatea building emergency condition, operate the one or more lightingcomponents of the halo light system to indicate the building emergencycondition to the user, and operate the display device to display thebuilding emergency condition to the user.

In some embodiments, a halo LED system further comprises one or morewaveguides, wherein each of the one or more waveguides is associatedwith one of one or more LEDs of the halo LED system, wherein each of theone or more waveguides is configured to transmit light from one of theone or more LEDs to the halo diffuser, wherein each of the one or morewaveguides is coupled to the halo diffuser at a first end of the one ormore waveguides and is proximate to one of the one or more LEDs at asecond end of the one or more waveguides.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a drawing of a building equipped with a HVAC system, accordingto an exemplary embodiment.

FIG. 2 is a drawing of multiple zones and floors of the building of FIG.1 equipped with control devices, according to an exemplary embodiment.

FIG. 3 is a block diagram of a waterside system that may be used inconjunction with the building of FIGS. 1-2, according to an exemplaryembodiment.

FIG. 4 is a block diagram of an airside system that may be used inconjunction with the building of FIGS. 1-2, according to an exemplaryembodiment.

FIG. 5 is a drawing of the connections of the control device of FIG. 2and FIG. 4, according to an exemplary embodiment.

FIG. 6 is a diagram of a communications system located in the buildingof FIGS. 1 and 2, according to an exemplary embodiment.

FIG. 7 is a block diagram illustrating the control device of FIGS. 2, 3,and 5 in greater detail, according to an exemplary embodiment.

FIG. 8 is a block diagram illustrating the control device of FIG. 7connected to three routers located in the building of FIGS. 1 and 2,according to an exemplary embodiment.

FIG. 9 is a flow diagram illustrating a process for determining thelocation of a mobile device in the building of FIG. 1 using theplurality of wireless emitters, according to an exemplary embodiment.

FIG. 10 is a drawing of a floorplan of a building with a main controlunit in one room and sensor units in other rooms, according to anexemplary embodiments.

FIG. 11 is a diagram illustrating the control device of FIG. 7 receivingoccupancy data, according to an exemplary embodiment.

FIG. 12 is a drawing of a building space and an occupant trackingapplication on the control device of FIG. 7, according to an exemplaryembodiment.

FIG. 13 is a flowchart of operations for controlling zones of a buildingwith the control device of FIG. 11, according to an exemplaryembodiment.

FIG. 14A is a flowchart of operations for controlling zones of abuilding with the control device of FIG. 11, according to an exemplaryembodiment.

FIG. 14B is a table of occupant permissions and preferences for thecontrol device of FIG. 7, according to an exemplary embodiment.

FIG. 15 is a diagram of the control device of FIG. 7 receiving emergencyand weather notifications, according to an exemplary embodiment.

FIG. 16A is a flowchart of operations for receiving emergencyinformation with the control device of FIG. 7, according to an exemplaryembodiment.

FIG. 16B is a flowchart of operations for prioritizing messages and datastreams with the control device of FIG. 7, according to an exemplaryembodiment.

FIG. 17 is a drawing of the control device of FIG. 15 displaying anemergency warning, according to an exemplary embodiment.

FIG. 18 is a drawing of the control device of FIG. 15 displaying anevacuation route, according to an exemplary embodiment.

FIG. 19 is a drawing illustrating the control device of FIG. 7 compilinga grocery list, according to an exemplary embodiment.

FIG. 20 is a flowchart of operations for compiling a grocery list withthe control device of FIG. 19, according to an exemplary embodiment.

FIG. 21 is a diagram of the control device of FIG. 7 communicating withhealth related devices and systems, according to an exemplaryembodiment.

FIG. 22 is a drawing of a medical application for the control device ofFIG. 21, according to an exemplary embodiment.

FIG. 23 is a drawing of another medical application for the controldevice of FIG. 21, according to an exemplary embodiment.

FIG. 24 is a diagram of the control device of FIG. 21 monitoring thehealth of an individual, according to an exemplary embodiment.

FIG. 25 is a drawing of a medical emergency screen displayed by thecontrol device of FIG. 21, according to an exemplary embodiment.

FIG. 26A is a diagram of the control device of FIG. 7 for hotel use,according to an exemplary embodiment.

FIG. 26B is a flow diagram of operations for scheduling hotelreservations with the control device of FIG. 7, according to anexemplary embodiment.

FIG. 27 is a flow diagram of operations for calling a taxi with thecontrol device of FIG. 7, according to an exemplary embodiment.

FIG. 28 is a set of drawings of screen displays for selecting roompreference of a hotel with the control device of FIG. 7, according to anexemplary embodiment.

FIG. 29 is a flow diagram of operations for preparing a hotel room foran occupant with the control device of FIG. 7, according to an exemplaryembodiment.

FIG. 30 is a flow diagram of operations for communicating with a frontdesk with the control device of FIG. 7, according to an exemplaryembodiment.

FIG. 31 is a flow diagram of operations for using a concierge feature ofthe control device of FIG. 7, according to an exemplary embodiment.

FIG. 32 is another flow diagram of operations for using a conciergefeature of the control device of FIG. 7, according to an exemplaryembodiment.

FIG. 33 is a flow diagram of operations for requesting hotelaccommodations with the control device of FIG. 7, according to anexemplary embodiment.

FIG. 34 is a flow diagram of operations for checking out of a hotel roomwith the control device of FIG. 7, according to an exemplary embodiment.

FIG. 35 is a block diagram illustrating the payment module of FIG. 7 ingreater detail, according to an exemplary embodiment.

FIG. 36 is a block diagram illustrating the input device of FIG. 7 ingreater detail, according to an exemplary embodiment.

FIG. 37 is a drawing illustrating the control device of FIG. 7 receivinga payment, according to an exemplary embodiment.

FIG. 38 is another drawing illustrating the control device of FIG. 7receiving a payment, according to an exemplary embodiment.

FIG. 39 is a flowchart of operations for processing a transaction withthe control device of FIG. 7, according to an exemplary embodiment.

FIG. 40 is a block diagram of a communications system located in thebuilding of FIG. 1, according to an exemplary embodiment.

FIG. 41 is a block diagram of a communications system located in thebuilding of FIG. 40 where the display devices are communicating ad hoc,according to an exemplary embodiment.

FIG. 42 is a block diagram illustrating the display device of FIGS.40-41 in greater detail, according to an exemplary embodiment.

FIG. 43 is a block diagram illustrating another embodiment of thedisplay device of FIGS. 40-41 in greater detail, according to anexemplary embodiment.

FIG. 44 is a block diagram illustrating another embodiment of thedisplay device of FIGS. 40-41 in greater detail, according to anexemplary embodiment.

FIG. 45 is a flow diagram of operations for prioritizing directions anddisplaying the directions on the display device of FIGS. 40-44,according to an exemplary embodiment.

FIG. 46 is a flow diagram of operations for handing off directionsbetween multiple display devices of FIGS. 40-44, according to anexemplary embodiment.

FIG. 47 is a flow diagram of operations for detaching the display deviceof FIGS. 4-8 from the wall in an emergency situation, according to anexemplary embodiment.

FIG. 48 is a drawing of the display device of FIGS. 40-44 displaying anemergency warning, according to an exemplary embodiment.

FIG. 49 is a drawing of the display device of FIGS. 40-44 displaying abuilding event notification, according to an exemplary embodiment.

FIG. 50 is a drawing of the display device of FIGS. 40-44 displaying aroute notification, according to an exemplary embodiment.

FIG. 51 is a drawing of the display device of FIGS. 40-44 displaying ahandicap route notification, according to an exemplary embodiment.

FIG. 52 is a drawing of the display device of FIGS. 40-44 displaying anemergency direction, according to an exemplary embodiment.

FIG. 53 is an isometric view of a display device, according to someembodiments.

FIG. 54 is a side view of the display device of FIG. 53, according tosome embodiments.

FIG. 55 is a rear view of the display device of FIG. 53, according tosome embodiments.

FIG. 56 is a rear elevated view of the display device of FIG. 53,according to some embodiments.

FIG. 57 is a top view of the display device of FIG. 53, according tosome embodiments.

FIG. 58 is a top view of the display device of FIG. 53, according tosome embodiments.

FIG. 59 is a top view of the display device of FIG. 53, according tosome embodiments.

FIG. 60 is a rear elevated view of a front portion of the display deviceof FIG. 53, according to some embodiments.

FIG. 61 is a front elevated view of the front portion of FIG. 60,according to some embodiments.

FIG. 62 is a front isometric view of the front portion of FIG. 60,according to some embodiments.

FIG. 63 is an isometric view of a rear portion of the display device ofFIG. 53, shown to include an LED board, according to some embodiments.

FIG. 64 is a front view of the LED board of FIG. 63, according to someembodiments.

FIG. 65 is a front view of the LED board of FIG. 63, according to someembodiments.

FIG. 66 is a side view of a portion of the display device of FIG. 53,shown to include a halo, according to some embodiments.

FIG. 67 is a front view of the halo of FIG. 66, according to someembodiments.

FIG. 68 is a rear elevated view of the halo of FIG. 66, shown to includelight guiding elements, according to some embodiments.

FIG. 69 is an elevated view of one of the light guiding elements of FIG.68, according to some embodiments.

FIG. 70 is a side view of one of the light guiding elements of FIG. 68,shown receiving light from an LED, according to some embodiments.

FIG. 71 is a side view of the halo of FIG. 66, shown to include lightguiding elements receiving light emitted by LEDs and guiding the emittedlight, according to some embodiments.

FIG. 72 is a block diagram of an LED controller, according to someembodiments.

FIG. 73 is a schematic drawing of the control device of FIG. 2 includinga halo diffusing light around a base portion of the control device,according to an exemplary embodiment.

FIG. 74 is a schematic drawing of the control device of FIG. 2 includinga halo diffusing light around a display screen of the control device,according to an exemplary embodiment.

FIG. 75 is a block diagram illustrating the control device of FIGS.73-74 in greater detail for operating the halos of FIGS. 73-74 toindicate emergency conditions, according to an exemplary embodiment.

FIG. 76 is a flow diagram of a process of operating the halos of FIGS.73-74 to indicate emergency conditions by the control device of FIGS.73-74, according to an exemplary embodiment.

FIG. 77 is a flow diagram of a process for displaying non-emergencyinformation of a first data stream and overriding the display of thenon-emergency information of the first data stream based on a seconddata stream that can be performed by the control device of FIGS. 73-74,according to an exemplary embodiment.

DETAILED DESCRIPTION Overview

Referring generally to the FIGURES, a user control device is shown,according to various exemplary embodiments. The thermostat describedherein may be used in any HVAC system, room, environment, or systemwithin which it is desired to control and/or observe environmentalconditions (e.g., temperature, humidity, etc.). In traditional HVACsystems, a thermostat may be adjusted by a user to control thetemperature of a system.

The user control device is intended to provide the user with an abilityto function as a connected smart hub. The thermostat provides adesirable user interface for other environmental controls because of itsknown fixed location within a space. The user control device is intendedto be more personal, more efficient, and more aware than traditionalthermostats.

The user control device collects data about a space and the occupants ofthe space with various sensors (e.g., temperature sensors, humiditysensors, acoustic sensors, optical sensors, gas and other chemicalsensors, biometric sensors, motion sensors, etc.) and user inputs. Theuser control device may utilize data collected from a single room,multiple rooms, an entire building, or multiple buildings. The data maybe analyzed locally by the user control device or may be uploaded to aremote computing system and/or the cloud for further analysis andprocessing.

Building Management System and HVAC System

Referring now to FIGS. 1-4, an exemplary building management system(BMS) and HVAC system in which the systems and methods of the presentdisclosure may be implemented are shown, according to an exemplaryembodiment. Referring particularly to FIG. 1, a perspective view of abuilding 10 is shown. Building 10 is served by a BMS. A BMS is, ingeneral, a system of devices configured to control, monitor, and manageequipment in or around a building or building area. A BMS can include,for example, a HVAC system, a security system, a lighting system, a firealerting system, any other system that is capable of managing buildingfunctions or devices, or any combination thereof.

The BMS that serves building 10 includes an HVAC system 100. HVAC system100 may include a plurality of HVAC devices (e.g., heaters, chillers,air handling units, pumps, fans, thermal energy storage, etc.)configured to provide heating, cooling, ventilation, or other servicesfor building 10. For example, HVAC system 100 is shown to include awaterside system 120 and an airside system 130. Waterside system 120 mayprovide a heated or chilled fluid to an air handling unit of airsidesystem 130. Airside system 130 may use the heated or chilled fluid toheat or cool an airflow provided to building 10. An exemplary watersidesystem and airside system which may be used in HVAC system 100 aredescribed in greater detail with reference to FIGS. 2-3.

HVAC system 100 is shown to include a chiller 102, a boiler 104, and arooftop air handling unit (AHU) 106. Waterside system 120 may use boiler104 and chiller 102 to heat or cool a working fluid (e.g., water,glycol, etc.) and may circulate the working fluid to AHU 106. In variousembodiments, the HVAC devices of waterside system 120 may be located inor around building 10 (as shown in FIG. 1) or at an offsite locationsuch as a central plant (e.g., a chiller plant, a steam plant, a heatplant, etc.). The working fluid may be heated in boiler 104 or cooled inchiller 102, depending on whether heating or cooling is required inbuilding 10. Boiler 104 may add heat to the circulated fluid, forexample, by burning a combustible material (e.g., natural gas) or usingan electric heating element. Chiller 102 may place the circulated fluidin a heat exchange relationship with another fluid (e.g., a refrigerant)in a heat exchanger (e.g., an evaporator) to absorb heat from thecirculated fluid. The working fluid from chiller 102 and/or boiler 104may be transported to AHU 106 via piping 108.

AHU 106 may place the working fluid in a heat exchange relationship withan airflow passing through AHU 106 (e.g., via one or more stages ofcooling coils and/or heating coils). The airflow may be, for example,outside air, return air from within building 10, or a combination ofboth. AHU 106 may transfer heat between the airflow and the workingfluid to provide heating or cooling for the airflow. For example, AHU106 may include one or more fans or blowers configured to pass theairflow over or through a heat exchanger containing the working fluid.The working fluid may then return to chiller 102 or boiler 104 viapiping 110.

Airside system 130 may deliver the airflow supplied by AHU 106 (i.e.,the supply airflow) to building 10 via air supply ducts 112 and mayprovide return air from building 10 to AHU 106 via air return ducts 114.In some embodiments, airside system 130 includes multiple variable airvolume (VAV) units 116. For example, airside system 130 is shown toinclude a separate VAV unit 116 on each floor or zone of building 10.VAV units 116 may include dampers or other flow control elements thatcan be operated to control an amount of the supply airflow provided toindividual zones of building 10. In other embodiments, airside system130 delivers the supply airflow into one or more zones of building 10(e.g., via supply ducts 112) without using intermediate VAV units 116 orother flow control elements. AHU 106 may include various sensors (e.g.,temperature sensors, pressure sensors, etc.) configured to measureattributes of the supply airflow. AHU 106 may receive input from sensorslocated within AHU 106 and/or within the building zone and may adjustthe flow rate, temperature, or other attributes of the supply airflowthrough AHU 106 to achieve setpoint conditions for the building zone.

Referring now to FIG. 2, building 10 is shown in greater detail,according to an exemplary embodiment. Building 10 may have multiplezones. In FIG. 2, building 10 has zones, 202, 204, 206, 208, 210, and212. In building 10, the zones each correspond to a separate floor. Invarious embodiments, the zones of building 10 may be rooms, sections ofa floor, multiple floors, etc. Each zone may have a correspondingcontrol device 214. In some embodiments, control device 214 is at leastone of a thermostat, a sensor, a controller, a display device, aconcierge device, a medical monitor device, etc. Control device 214 maytake input from users. The input may be an environmental setpoint, aconcierge question, a payment, etc. In some embodiments, control device214 can cause music and/or building announcements to be played in one ormore of zones 202-212, cause the temperature and/or humidity to beregulated in one or more of zones 202-212, and/or any other controlaction.

In some embodiments, control device 214 can monitor the health of anoccupant 216 of building 10. In some embodiments, control device 214monitors heat signatures, heartrates, and any other information that canbe collected from cameras, medical devices, and/or any other healthrelated sensor. In some embodiments, building 10 has wirelesstransmitters 218 in each or some of zones 202-212. The wirelesstransmitters 218 may be routers, coordinators, and/or any other devicebroadcasting radio waves. In some embodiments, wireless transmitters 218form a Wi-Fi network, a Zigbee network, a Bluetooth network, and/or anyother kind of network.

In some embodiments, occupant 216 has a mobile device that cancommunicate with wireless transmitters 218. Control device 214 may usethe signal strengths between the mobile device of occupant 216 and thewireless transmitters 218 to determine what zone the occupant is in. Insome embodiments, control device 214 causes temperature setpoints, musicand/or other control actions to follow occupant 216 as the occupant 216moves from one zone to another zone (i.e., from one floor to anotherfloor).

In some embodiments, control devices 214 are connected to a buildingmanagement system, a weather server, and/or a building emergencysensor(s). In some embodiments, control devices 214 may receiveemergency notifications from the building management system, the weatherserver, and/or the building emergency sensor(s). Based on the nature ofthe emergency, control devices 214 may give directions to an occupant ofthe building. In some embodiments, the direction may be to respond to anemergency (e.g., call the police, hide and turn the lights off, etc.) Invarious embodiments, the directions given to the occupant (e.g.,occupant 216) may be navigation directions. For example, zone 212 may bea safe zone with no windows an individual (e.g., occupant 216). Ifcontrol devices 214 determines that there are high winds around building10, the control device 214 may direct occupants of zones 202-210 to zone212 if zone 212 has no windows.

Referring now to FIG. 3, a block diagram of a waterside system 300 isshown, according to an exemplary embodiment. In various embodiments,waterside system 300 may supplement or replace waterside system 120 inHVAC system 100 or may be implemented separate from HVAC system 100.When implemented in HVAC system 100, waterside system 300 may include asubset of the HVAC devices in HVAC system 100 (e.g., boiler 104, chiller102, pumps, valves, etc.) and may operate to supply a heated or chilledfluid to AHU 106. The HVAC devices of waterside system 300 may belocated within building 10 (e.g., as components of waterside system 120)or at an offsite location such as a central plant.

In FIG. 3, waterside system 300 is shown as a central plant having aplurality of subplants 302-312. Subplants 302-312 are shown to include aheater subplant 302, a heat recovery chiller subplant 304, a chillersubplant 306, a cooling tower subplant 308, a hot thermal energy storage(TES) subplant 310, and a cold thermal energy storage (TES) subplant312. Subplants 302-312 consume resources (e.g., water, natural gas,electricity, etc.) from utilities to serve the thermal energy loads(e.g., hot water, cold water, heating, cooling, etc.) of a building orcampus. For example, heater subplant 302 may be configured to heat waterin a hot water loop 314 that circulates the hot water between heatersubplant 302 and building 10. Chiller subplant 306 may be configured tochill water in a cold water loop 316 that circulates the cold waterbetween chiller subplant 306 building 10. Heat recovery chiller subplant304 may be configured to transfer heat from cold water loop 316 to hotwater loop 314 to provide additional heating for the hot water andadditional cooling for the cold water. Condenser water loop 318 mayabsorb heat from the cold water in chiller subplant 306 and reject theabsorbed heat in cooling tower subplant 308 or transfer the absorbedheat to hot water loop 314. Hot TES subplant 310 and cold TES subplant312 may store hot and cold thermal energy, respectively, for subsequentuse.

Hot water loop 314 and cold water loop 316 may deliver the heated and/orchilled water to air handlers located on the rooftop of building 10(e.g., AHU 106) or to individual floors or zones of building 10 (e.g.,VAV units 116). The air handlers push air past heat exchangers (e.g.,heating coils or cooling coils) through which the water flows to provideheating or cooling for the air. The heated or cooled air may bedelivered to individual zones of building 10 to serve the thermal energyloads of building 10. The water then returns to subplants 302-312 toreceive further heating or cooling.

Although subplants 302-312 are shown and described as heating andcooling water for circulation to a building, it is understood that anyother type of working fluid (e.g., glycol, CO2, etc.) may be used inplace of or in addition to water to serve the thermal energy loads. Inother embodiments, subplants 302-312 may provide heating and/or coolingdirectly to the building or campus without requiring an intermediateheat transfer fluid. These and other variations to waterside system 300are within the teachings of the present disclosure.

Each of subplants 302-312 may include a variety of equipment configuredto facilitate the functions of the subplant. For example, heatersubplant 302 is shown to include a plurality of heating elements 320(e.g., boilers, electric heaters, etc.) configured to add heat to thehot water in hot water loop 314. Heater subplant 302 is also shown toinclude several pumps 322 and 324 configured to circulate the hot waterin hot water loop 314 and to control the flow rate of the hot waterthrough individual heating elements 320. Chiller subplant 306 is shownto include a plurality of chillers 332 configured to remove heat fromthe cold water in cold water loop 316. Chiller subplant 306 is alsoshown to include several pumps 334 and 336 configured to circulate thecold water in cold water loop 316 and to control the flow rate of thecold water through individual chillers 332.

Heat recovery chiller subplant 304 is shown to include a plurality ofheat recovery heat exchangers 326 (e.g., refrigeration circuits)configured to transfer heat from cold water loop 316 to hot water loop314. Heat recovery chiller subplant 304 is also shown to include severalpumps 328 and 330 configured to circulate the hot water and/or coldwater through heat recovery heat exchangers 326 and to control the flowrate of the water through individual heat recovery heat exchangers 226.Cooling tower subplant 208 is shown to include a plurality of coolingtowers 338 configured to remove heat from the condenser water incondenser water loop 318. Cooling tower subplant 308 is also shown toinclude several pumps 340 configured to circulate the condenser water incondenser water loop 318 and to control the flow rate of the condenserwater through individual cooling towers 338.

Hot TES subplant 310 is shown to include a hot TES tank 342 configuredto store the hot water for later use. Hot TES subplant 310 may alsoinclude one or more pumps or valves configured to control the flow rateof the hot water into or out of hot TES tank 342. Cold TES subplant 312is shown to include cold TES tanks 344 configured to store the coldwater for later use. Cold TES subplant 312 may also include one or morepumps or valves configured to control the flow rate of the cold waterinto or out of cold TES tanks 344.

In some embodiments, one or more of the pumps in waterside system 300(e.g., pumps 322, 324, 328, 330, 334, 336, and/or 340) or pipelines inwaterside system 300 include an isolation valve associated therewith.Isolation valves may be integrated with the pumps or positioned upstreamor downstream of the pumps to control the fluid flows in watersidesystem 300. In various embodiments, waterside system 300 may includemore, fewer, or different types of devices and/or subplants based on theparticular configuration of waterside system 300 and the types of loadsserved by waterside system 300.

Referring now to FIG. 4, airside system 400 is shown to include aneconomizer-type air handling unit (AHU) 402. Economizer-type AHUs varythe amount of outside air and return air used by the air handling unitfor heating or cooling. For example, AHU 402 may receive return air 404from building zone 406 via return air duct 408 and may deliver supplyair 410 to building zone 406 via supply air duct 612. In someembodiments, AHU 402 is a rooftop unit located on the roof of building10 (e.g., AHU 402 as shown in FIG. 1) or otherwise positioned to receiveboth return air 404 and outside air 414. AHU 402 may be configured tooperate exhaust air damper 416, mixing damper 418, and outside airdamper 420 to control an amount of outside air 414 and return air 404that combine to form supply air 410. Any return air 404 that does notpass through mixing damper 418 may be exhausted from AHU 402 throughexhaust damper 416 as exhaust air 422.

Each of dampers 416-420 may be operated by an actuator. For example,exhaust air damper 416 may be operated by actuator 424, mixing damper418 may be operated by actuator 426, and outside air damper 420 may beoperated by actuator 428. Actuators 424-428 may communicate with an AHUcontroller 430 via a communications link 432. Actuators 424-428 mayreceive control signals from AHU controller 430 and may provide feedbacksignals to AHU controller 430. Feedback signals may include, forexample, an indication of a current actuator or damper position, anamount of torque or force exerted by the actuator, diagnosticinformation (e.g., results of diagnostic tests performed by actuators424-428), status information, commissioning information, configurationsettings, calibration data, and/or other types of information or datathat may be collected, stored, or used by actuators 424-428. AHUcontroller 430 may be an economizer controller configured to use one ormore control algorithms (e.g., state-based algorithms, extremum seekingcontrol (ESC) algorithms, proportional-integral (PI) control algorithms,proportional-integral-derivative (PID) control algorithms, modelpredictive control (MPC) algorithms, feedback control algorithms, etc.)to control actuators 424-428.

Still referring to FIG. 4, AHU 402 is shown to include a cooling coil434, a heating coil 436, and a fan 438 positioned within supply air duct612. Fan 438 may be configured to force supply air 410 through coolingcoil 434 and/or heating coil 436 and provide supply air 410 to buildingzone 406. AHU controller 430 may communicate with fan 438 viacommunications link 440 to control a flow rate of supply air 410. Insome embodiments, AHU controller 430 controls an amount of heating orcooling applied to supply air 410 by modulating a speed of fan 438.

Cooling coil 434 may receive a chilled fluid from waterside system 200(e.g., from cold water loop 316) via piping 442 and may return thechilled fluid to waterside system 200 via piping 444. Valve 446 may bepositioned along piping 442 or piping 444 to control a flow rate of thechilled fluid through cooling coil 474. In some embodiments, coolingcoil 434 includes multiple stages of cooling coils that can beindependently activated and deactivated (e.g., by AHU controller 430, byBMS controller 466, etc.) to modulate an amount of cooling applied tosupply air 410.

Heating coil 436 may receive a heated fluid from waterside system 200(e.g., from hot water loop 314) via piping 448 and may return the heatedfluid to waterside system 200 via piping 450. Valve 452 may bepositioned along piping 448 or piping 450 to control a flow rate of theheated fluid through heating coil 436. In some embodiments, heating coil436 includes multiple stages of heating coils that can be independentlyactivated and deactivated (e.g., by AHU controller 430, by BMScontroller 466, etc.) to modulate an amount of heating applied to supplyair 410.

Each of valves 446 and 452 may be controlled by an actuator. Forexample, valve 446 may be controlled by actuator 454 and valve 452 maybe controlled by actuator 456. Actuators 454-456 may communicate withAHU controller 430 via communications links 458-460. Actuators 454-456may receive control signals from AHU controller 430 and may providefeedback signals to controller 430. In some embodiments, AHU controller430 receives a measurement of the supply air temperature from atemperature sensor 462 positioned in supply air duct 612 (e.g.,downstream of cooling coil 434 and/or heating coil 436). AHU controller430 may also receive a measurement of the temperature of building zone406 from a temperature sensor 464 located in building zone 406.

In some embodiments, AHU controller 430 operates valves 446 and 452 viaactuators 454-456 to modulate an amount of heating or cooling providedto supply air 410 (e.g., to achieve a set point temperature for supplyair 410 or to maintain the temperature of supply air 410 within a setpoint temperature range). The positions of valves 446 and 452 affect theamount of heating or cooling provided to supply air 410 by cooling coil434 or heating coil 436 and may correlate with the amount of energyconsumed to achieve a desired supply air temperature. AHU controller 430may control the temperature of supply air 410 and/or building zone 406by activating or deactivating coils 434-436, adjusting a speed of fan438, or a combination of both.

Still referring to FIG. 4, airside system 400 is shown to include abuilding management system (BMS) controller 466 and a control device214. BMS controller 466 may include one or more computer systems (e.g.,servers, supervisory controllers, subsystem controllers, etc.) thatserve as system level controllers, application or data servers, headnodes, or master controllers for airside system 400, waterside system200, HVAC system 100, and/or other controllable systems that servebuilding 10. BMS controller 466 may communicate with multiple downstreambuilding systems or subsystems (e.g., HVAC system 100, a securitysystem, a lighting system, waterside system 200, etc.) via acommunications link 470 according to like or disparate protocols (e.g.,LON, BACnet, etc.). In various embodiments, AHU controller 430 and BMScontroller 466 may be separate (as shown in FIG. 4) or integrated. In anintegrated implementation, AHU controller 430 may be a software moduleconfigured for execution by a processor of BMS controller 466.

In some embodiments, AHU controller 430 receives information from BMScontroller 466 (e.g., commands, set points, operating boundaries, etc.)and provides information to BMS controller 466 (e.g., temperaturemeasurements, valve or actuator positions, operating statuses,diagnostics, etc.). For example, AHU controller 430 may provide BMScontroller 466 with temperature measurements from temperature sensors462-464, equipment on/off states, equipment operating capacities, and/orany other information that can be used by BMS controller 466 to monitoror control a variable state or condition within building zone 406.

Control device 214 may include one or more of the user control devices.Control device 214 may include one or more human-machine interfaces orclient interfaces (e.g., graphical user interfaces, reportinginterfaces, text-based computer interfaces, client-facing web services,web servers that provide pages to web clients, etc.) for controlling,viewing, or otherwise interacting with HVAC system 100, its subsystems,and/or devices. Control device 214 may be a computer workstation, aclient terminal, a remote or local interface, or any other type of userinterface device. Control device 214 may be a stationary terminal or amobile device. For example, control device 214 may be a desktopcomputer, a computer server with a user interface, a laptop computer, atablet, a smartphone, a PDA, or any other type of mobile or non-mobiledevice. Control device 214 may communicate with BMS controller 466and/or AHU controller 430 via communications link 472.

Referring now to FIG. 5, control device 214 is shown as a connectedsmart hub or private area network (PAN), according to some embodiments.Control device 214 may include a variety of sensors and may beconfigured to communicate with a variety of external systems or devices.For example, control device 214 may include temperature sensors 502,speakers 504, leak detection system 508, health monitoring sensors 510,humidity sensors 514, occupancy sensors 516, light detection sensors518, proximity sensor 520, carbon dioxide sensors 522, or any of avariety of other sensors. Alternatively, control device 214 may receiveinput from external sensors configured to measure such variables. Theexternal sensors may not communicate over a PAN network but maycommunicate with control device 214 via an IP based network and/or theInternet.

In some embodiments, speakers 504 are located locally as a component ofcontrol device 214. Speakers 504 may be low power speakers used forplaying audio to the immediate occupant of control device 214 and/oroccupants of the zone in which control device 214 is located. In someembodiments, speakers 504 may be remote speakers connected to controldevice 214 via a network. In some embodiments, speakers 504 are abuilding audio system, an emergency alert system, and/or alarm systemconfigured to broadcast building wide and/or zone messages or alarms.

Control device 214 may communicate with a remote camera 506, a shadecontrol system 512, a leak detection system 508, a HVAC system, or anyof a variety of other external systems or devices which may be used in ahome automation system or a building automation system. Control device214 may provide a variety of monitoring and control interfaces to allowa user to control all of the systems and devices connected to controldevice 214. Exemplary user interfaces and features of control device 214are described in greater detail below.

Referring now to FIG. 6, a block diagram of communications system 600 isshown, according to an exemplary embodiment. System 600 can beimplemented in a building (e.g. building 10) and is shown to includecontrol device 214, network 602, healthcare sensor(s) 604, buildingemergency sensor(s) 606, weather server(s) 608, building managementsystem 610, and user device 612. System 600 connects devices, systems,and servers via network 602 so that building information, HVAC controls,emergency information, navigation directions, and other information canbe passed between devices (e.g., control device 214, user device 612,and/or building emergency sensor(s) 606 and servers and systems (e.g.,weather server(s) 608 and/or building management system 610). In someembodiments, control device 214 is connected to speakers 504 asdescribed with reference to FIG. 5.

In some embodiments, network 602 communicatively couples the devices,systems, and servers of system 600. In some embodiments, network 602 isat least one of and/or a combination of a Wi-Fi network, a wiredEthernet network, a Zigbee network, and a Bluetooth network. Network 602may be a local area network or a wide area network (e.g., the Internet,a building WAN, etc.) and may use a variety of communications protocols(e.g., BACnet, IP, LON, etc.) Network 602 may include routers, modems,and/or network switches.

In some embodiments, control device 214 is configured to receiveemergency information, navigation directions, occupant information,concierge information, and any other information via network 602. Insome embodiments, the information is received from building managementsystem 610 via network 602. In various embodiments, the information isreceived from the Internet via network 602. In some embodiments, controldevice 214 is at least one of or a combination of a thermostat, ahumidistat, a light controller, and any other wall mounted and/or handheld device. In some embodiments, control device 214 is connected tobuilding emergency sensor(s) 606. In some embodiments, buildingemergency sensor(s) 606 are sensors which detect building emergencies.Building emergency sensor(s) 606 may be smoke detectors, carbon monoxidedetectors, carbon dioxide detectors (e.g., carbon dioxide sensors 522),an emergency button (e.g., emergency pull handles, panic buttons, amanual fire alarm button and/or handle, etc.) and/or any other emergencysensor. In some embodiments, the emergency sensor(s) include actuators.The actuators may be building emergency sirens and/or building audiospeaker systems (e.g., speakers 504), automatic door and/or windowcontrol (e.g., shade control system 512), and any other actuator used ina building.

In some embodiments, control device 214 may be communicatively coupledto weather server(s) 608 via network 602. In some embodiments, thecontrol device 214 may be configured to receive weather alerts (e.g.,high and low daily temperature, five-day forecast, thirty-day forecast,etc.) from weather server(s) 608. Control device 214 may be configuredto receive emergency weather alerts (e.g., flood warnings, firewarnings, thunder storm warnings, winter storm warnings, etc.) In someembodiments, control device 214 may be configured to display emergencywarnings via a user interface of control device 214 when control device214 receives an emergency weather alert from weather server(s) 608. Thecontrol device 214 may be configured to display emergency warnings basedon the data received from building emergency sensor(s) 606. In someembodiments, the control device 214 may cause a siren (e.g., speakers504 and/or building emergency sensor(s) 606) to alert occupants of thebuilding of an emergency, cause all doors to become locked and/orunlocked, cause an advisory message be broadcast through the building,and control any other actuator or system necessary for responding to abuilding emergency.

In some embodiments, control device 214 is configured to communicatewith building management system 610 via network 602. Control device 214may be configured to transmit environmental setpoints (e.g., temperaturesetpoint, humidity setpoint, etc.) to building management system 610. Insome embodiments, building management system 610 may be configured tocause zones of a building (e.g., building 10) to be controlled to thesetpoint received from control device 214. In some embodiments, buildingmanagement system 610 may be configured to control the lighting of abuilding. In some embodiments, building management system 610 may beconfigured to transmit emergency information to control device 214. Insome embodiments, the emergency information is a notification of ashooter lockdown, a tornado warning, a flood warning, a thunderstormwarning, and/or any other warning. In some embodiments, buildingmanagement system 610 is connected to various weather servers or otherweb servers from which building management system 610 receives emergencywarning information. In various embodiments, building management systemis a computing system of a hotel. Building management system 610 maykeep track of hotel occupancy, may relay requests to hotel staff, and/orperform any other functions of a hotel computing system.

Control device 214 is configured to communicate with user device 612 vianetwork 602. In some embodiments, user device 612 is a smartphone, atablet, a laptop computer, and/or any other mobile and/or stationarycomputing device. In some embodiments, user device 612 communicatescalendar information to control device 214. In some embodiments, thecalendar information is stored and/or entered by a user into a calendarapplication. In some embodiments, calendar application is at least oneof Outlook, Google Calendar, Fantastical, Shifts, CloudCal, DigiCal,and/or any other calendar application. In some embodiments, controldevice 214 receives calendar information from the calendar applicationsuch as times and locations of appointments, times and locations ofmeetings, and/or any other information. Control device 214 may beconfigured to display building map direction to a user associated withuser device 612 and/or any other information.

In some embodiments, a user may press a button on a user interface ofcontrol device 214 indicating a building emergency. The user may be ableto indicate the type of emergency (e.g., fire, flood, active shooter,etc.) Control device 214 may communicate an alert to building managementsystem 610, user device 612, and any other device, system, and/orserver.

In some embodiments, control device 214 is communicably coupled tohealthcare sensor(s) 604 via network 602. In some embodiments, controldevice is configured to monitor healthcare sensor(s) 604 collecting datafor occupants of a building (e.g., building 10) and determine healthmetrics for the occupants based on the data received from the healthcaresensor(s) 604. In some embodiments, healthcare sensor(s) 604 are one ormore smart wrist bands, pacemakers, insulin pumps, and/or any othermedical device. The health metrics may be determined based on heartrates, insulin levels, and/or any other biological and/or medical data.

Referring now to FIG. 7, a block diagram illustrating control device 214in greater detail is shown, according to some embodiments. Controldevice 214 is shown to include a variety of user interface devices 702and sensors 714. User interface devices 702 may be configured to receiveinput from a user and provide output to a user in various forms. Forexample, user interface devices 702 are shown to include electronicdisplay 706, an electronic display 706, ambient lighting 708, speakers710 (e.g., speakers 504), and input device 712. In some embodiments,user interface devices 702 include a microphone configured to receivevoice commands from a user, a keyboard or buttons, switches, dials, orany other user-operable input devices. It is contemplated that userinterface devices 702 may include any type of device configured toreceive input from a user and/or provide an output to a user in any of avariety of forms (e.g., touch, text, video, graphics, audio, vibration,etc.).

Sensors 714 may be configured to measure a variable state or conditionof the environment in which control device 214 is installed. Forexample, sensors 714 are shown to include a temperature sensor 716, ahumidity sensor 718, an air quality sensor 720, a proximity sensor 722,a camera 724, a microphone 726, a light sensor 728, and a vibrationsensor 730. Air quality sensor 720 may be configured to measure any of avariety of air quality variables such as oxygen level, carbon dioxidelevel, carbon monoxide level, allergens, pollutants, smoke, etc.Proximity sensor 722 may include one or more sensors configured todetect the presence of people or devices proximate to control device214. For example, proximity sensor 722 may include a near-fieldcommunications (NFC) sensor, a radio frequency identification (RFID)sensor, a Bluetooth sensor, a capacitive proximity sensor, a biometricsensor, or any other sensor configured to detect the presence of aperson or device. Camera 724 may include a visible light camera, amotion detector camera, an infrared camera, an ultraviolet camera, anoptical sensor, or any other type of camera. Light sensor 728 may beconfigured to measure ambient light levels. Vibration sensor 730 may beconfigured to measure vibrations from earthquakes or other seismicactivity at the location of control device 214.

Still referring to FIG. 7, control device 214 is shown to include acommunications interface 732 and a processing circuit 734.Communications interface 732 may include wired or wireless interfaces(e.g., jacks, antennas, transmitters, receivers, transceivers, wireterminals, etc.) for conducting data communications with varioussystems, devices, or networks. For example, communications interface 732may include an Ethernet card and port for sending and receiving data viaan Ethernet-based communications network and/or a Wi-Fi transceiver forcommunicating via a wireless communications network. Communicationsinterface 732 may be configured to communicate via local area networksor wide area networks (e.g., the Internet, a building WAN, etc.) and mayuse a variety of communications protocols (e.g., BACnet, IP, LON, etc.).

Communications interface 732 may include a network interface configuredto facilitate electronic data communications between control device 214and various external systems or devices (e.g., network 602, buildingmanagement system 610, HVAC equipment 738, user device 612, etc.) Forexample, control device 214 may receive information from buildingmanagement system 610 or HVAC equipment 738 indicating one or moremeasured states of the controlled building (e.g., temperature, humidity,electric loads, etc.) and one or more states of the HVAC equipment 738(e.g., equipment status, power consumption, equipment availability,etc.). In some embodiments, HVAC equipment 738 may be lighting systems,building systems, actuators, chillers, heaters, and/or any otherbuilding equipment and/or system. Communications interface 732 mayreceive inputs from building management system 610 or HVAC equipment 738and may provide operating parameters (e.g., on/off decisions, setpoints, etc.) to building management system 610 or HVAC equipment 738.The operating parameters may cause building management system 610 toactivate, deactivate, or adjust a set point for various types of homeequipment or building equipment in communication with control device214.

Processing circuit 734 is shown to include a processor 740 and memory742. Processor 740 may be a general purpose or specific purposeprocessor, an application specific integrated circuit (ASIC), one ormore field programmable gate arrays (FPGAs), a group of processingcomponents, or other suitable processing components. Processor 740 maybe configured to execute computer code or instructions stored in memory742 or received from other computer readable media (e.g., CDROM, networkstorage, a remote server, etc.).

Memory 742 may include one or more devices (e.g., memory units, memorydevices, storage devices, etc.) for storing data and/or computer codefor completing and/or facilitating the various processes described inthe present disclosure. Memory 742 may include random access memory(RAM), read-only memory (ROM), hard drive storage, temporary storage,non-volatile memory, flash memory, optical memory, or any other suitablememory for storing software objects and/or computer instructions. Memory742 may include database components, object code components, scriptcomponents, or any other type of information structure for supportingthe various activities and information structures described in thepresent disclosure. Memory 742 may be communicably connected toprocessor 740 via processing circuit 734 and may include computer codefor executing (e.g., by processor 740) one or more processes describedherein. For example, memory 742 is shown to include a voice commandmodule 744, a building module 746, a voice control module 748, a paymentmodule 758, a hotel module 750, a healthcare module 752, an occupancymodule 754, and an emergency module 756. The functions of some of thesemodules is described in greater detail below.

In some embodiments, voice command module 744 is configured to receiveaudio data from microphone 726. Voice command module 744 may beconfigured to translate audio data into spoken words. In someembodiments, voice command module 744 may be configured to performInternet searches based on the spoken words via network 602. In variousembodiments, voice command module 744 may send requests to buildingmanagement system 610 based on the spoken words.

Occupancy Tracking Features

Referring now to FIG. 8, a block diagram of an occupancy tracking system800 is shown according to an exemplary embodiment. System 800 can beimplemented in a building space (e.g., building 10) to determine theoccupancy of the building space based on Wi-Fi router connections andsignal strengths. System 800 is shown to include building managementsystem 610, control device 214, network 602, routers 804-808, and userdevice 612. In some embodiments, building management system 610 operatesthe building space as described in FIGS. 1-4. In various embodiments,control device 214 operates the building space as described in FIGS.1-4. Building management system 610 is shown to be connected to controldevice 214 and routers 804-808. In some embodiments, network 602 is atleast one of and/or a combination of a Wi-Fi network, a wired Ethernetnetwork, a Zigbee network, and a Bluetooth network. Network 602 may be alocal area network or a wide area network (e.g., the Internet, abuilding WAN, etc.) and may use a variety of communications protocols(e.g., BACnet, IP, LON, etc.).

Building management system 610 may include an application server. Theapplication server may be a remote server and may be hosted at a remotelocation. The application server may be configured to provide aweb-based presence for users and/or building administrators to accessinformation regarding occupancy of the building. In some embodiments,the application server allows users and/or building administrators toview data pertaining to the number of users in the building space andtheir respective locations. The application server may communicate withuser device 612 through routers 804-808 or may communicate to userdevice 612 via mobile data (e.g. 1G, 2G, 3G, LTE, etc.).

In some embodiments, the application server integrates a buildingfacility web application with the determined number and location ofoccupants. In some embodiments, the building facility application maycontrol room, zone, building, and campus lighting, booking, publicservice announcements and other features of a building facility. In someembodiments, the building facility web application may identify a userwhen a device associated with the user (e.g., user device 612) isdetected in a room, zone, building and/or campus based on wirelesssignal strengths. The building facility web application mayautomatically login the identified user with the building web facilityapplication. A user that has been logged in may be able to changelighting, environmental setpoints and any other adjustable buildingfacility web application feature via user device 612. In someembodiments, the building facility web application may automaticallyadjust lighting and environmental setpoints to preferred settings of theidentified and logged in user.

Routers 804-808 may be installed for the specific purpose of determininguser occupancy or may be existing routers in a wireless buildingnetwork. In some embodiments, each router may have a unique ID. In FIG.8, router 804 has the ID B1, router 806 has the ID A1, and router 808has the ID C1. Routers 804-808 may connect user device 612 to theInternet and/or control device 214 through network 602. Although onlythree routers 804-808 are shown in FIG. 8, it is contemplated thatsystem 800 can include any number of routers located in the buildingspace.

Routers 804-808 can be configured to emit, receive, sense, relay, orotherwise engage in unidirectional or bidirectional wirelesscommunications. Routers 804-808 can use any type wireless technology orcommunications protocol. For example, in various embodiments, thewireless emitters/receivers can be Bluetooth low energy (BLE) emitters,near field communications (NFC) devices, Wi-Fi transceivers, RFIDdevices, ultrawide band (UWB) devices, infrared emitters/sensors,visible light communications (VLC) devices, ultrasound devices, cellulartransceivers, iBeacons, or any other type of hardware configured tofacilitate wireless data communications. In some embodiments, routers804-808 are integrated with various devices within the building (e.g.,thermostats, lighting sensors, zone controllers).

Routers 804-808 can broadcast a wireless signal. The wireless signalbroadcast by routers 804-808 can include the identifier associated withrouters 804-808. For example, routers 804-808 can broadcast a SSID, MACaddress, or other identifier which can be used to identify a particularrouter. In some embodiments, the wireless signal broadcast by routers804-808 includes multiple emitter identifiers (e.g., a UUID value, amajor value, a minor value, etc.). User device 612 can detect thewireless signals emitted by the routers 804-808. User device 612 can beconfigured to identify the router associated with the wireless signal.In some embodiments, user device 612 detects the signal strength of thewireless signals for each of routers 804-808.

In FIG. 8, user device 612 communicates with routers 804-808. Userdevice 612 may communicate to the routers via Wi-Fi, Zigbee, Bluetooth,and/or any other wireless communication protocol. User device 612 maycommunicate to routers 804-808 and determine a signal strength of eachrouter. In some embodiments, received signal strength (RSSI) isdetermined by user device 612 for connections to each of routers804-808. In some embodiments, user device 612 detects the RSSI of thewireless signals received from each of routers 804-808 without engagingin bidirectional communications with any of routers 804-808. Forexample, user device 612 can passively detect or measure RSSI withoutactively sending any return data to routers 804-808. In variousembodiments, user device 612 determines RSSI as a percentage, in mW, indBm, and/or in any other unit or power ratio.

User device 612 may store the location of each router 804-808 in amemory device and may determine (e.g., triangulate, estimate, etc.) thelocation of user device 612 based on the stored locations of routers804-808 and the determined RSSI value for each router. In someembodiments, user device 612 is only connected to a single router oronly receives a wireless signal from a single router. User device 612may determine an approximate circular field around the single router inwhich user device 612 may be located based on the determined RSSI. Insome embodiments, the circular field is an approximate radius such as adistance that user device 612 may be located away from the router. Forexample, a strong RSSI may indicate that user device 612 is close to aparticular router, whereas a weaker RSSI may indicate that user device612 is further from the router. User device 612 can use a mapping tableor function to translate RSSI into distance. In some embodiments, thetranslation between RSSI and distance is a function of the router'sbroadcast power or other router settings, which user device 612 canreceive from each router within broadcast range. In some embodiments,the field is a range of radii. Each radii may be different and userdevice 612 may be located between the two radii in a disc shaped field.In various embodiments, user device 612 triangulates the location ofuser device 612 based on one or more signal strengths between knownlocations of routers.

In various embodiments, routers 804-808 send signal strengths betweenrouters 804-808 and user device 612 to control device 214. Controldevice 214 may store the location of each router 804-808 in a memorydevice and may determine (e.g., triangulate, estimate, etc.) thelocation of user device 612 based on the stored locations of routers804-808 and the determined RSSI value for each router. In someembodiments, user device 612 is only connected to a single router oronly receives a wireless signal from a single router. Control device 214may determine an approximate circular field around the single router inwhich user device 612 may be located based on the determined RSSI. Insome embodiments, the circular field is an approximate radius such as adistance that user device 612 may be located away from the router. Forexample, a strong RSSI may indicate that user device 612 is close to aparticular router, whereas a weaker RSSI may indicate that user device612 is further from the router. Control device 214 can use a mappingtable or function to translate RSSI into distance. In some embodiments,the translation between RSSI and distance is a function of the router'sbroadcast power or other router settings, which control device 214 canreceive from each router within broadcast range. In some embodiments,the field is a range of radii. Each radii may be different and userdevice 612 may be located between the two radii in a disc shaped field.In various embodiments, control device 214 triangulates the location ofuser device 612 based on one or more signal strengths between knownlocations of routers.

Still referring to FIG. 8, user device 612 may communicate with buildingmanagement system 610, an application server, and/or control device 214via the routers 804-808. In some embodiments, user device 612 sends itslocation within the building space to building management system 610, anapplication server, and/or control device 214. In some embodiments, userdevice 612 sends a unique ID to building management system 610 and/or anapplication server. In FIG. 8, the unique ID of user device 612 is PhoneA. In some embodiments, building management system 610 is configured torun a unique heating or cooling schedule based on the ID of the userdevice 612. For example, an environmental setpoint may be tied to the IDof user device 612. Building management system 610 may be configured toadjust the setpoint of the zone in which user device 612 is located tothe environmental setpoint tied to the ID of user device 612.

Referring now to FIG. 9, a flow diagram illustrating a process 900 forusing occupant location in a building is shown, according to anexemplary embodiment. A building (e.g., building 10) is equipped with aplurality of wireless emitters 902. Each of wireless emitters 902 may belocated at a different position in the building and may be associatedwith a different emitter identifier. Although only one wireless emitter902 is shown in FIG. 9, many wireless emitters 902 may be placed atvarious locations in or around the building. Each of wireless emitters902 broadcasts a wireless signal (step 904). The wireless signalbroadcast by emitter 902 includes an indication of an emitter identifierassociated with wireless emitter 902. In some embodiments, the wirelesssignal broadcast by emitter 902 include multiple emitter identifiers(e.g., a UUID value, a major value, a minor value, etc.)

Still referring to FIG. 9, a user device 612 detects the wireless signalemitted by wireless emitter 902 (step 906). User device 612 may be, forexample, a laptop computer, a tablet, a smart phone, a RFID sensor, aBluetooth device, a Wi-Fi device, a NFC device, a portablecommunications device, or any combination thereof. User device 612 maybe configured to run remote applications 908 and may function as a UIclient. User device 612 may be configured (e.g., by an applicationrunning on user device 612) to identify the emitter identifierassociated with the wireless signal detected in step 906.

In FIG. 9, user device 612 is shown connecting to an application gateway910 (e.g., at a predefined IP address, via a wireless data connection)and reporting the emitter identifier associated with the detectedwireless signal (step 912). In some embodiments, user device 612requests a user interface for presentation on user device 612. Therequest may include the emitter identifier detected by user device 612and/or a device identifier associated with user device 612. Applicationgateway 910 may provide the emitter identifier and/or the deviceidentifier to building management system 610. In various embodiments,application gateway 910 and building management system 610 may becombined into a single component or user device 612 may report theemitter identifier directly to building management system 610.

Building management system 610 uses the emitter identifier and/or thedevice identifier to select a user interface for presentation on userdevice 612. Building management system 610 may select the user interfacefor a building zone associated with the emitter identifier reported byuser device 612. For example, building management system 610 may selecta user interface which includes information and/or control optionsrelating to the building zone associated with the reported emitteridentifier. In some embodiments, building management system 610 selectsa user interface based on the identity of a user associated with userdevice 612 (e.g., based on a user identifier or device identifierreported by user device 612). In some embodiments, building managementsystem 610 uses emitter identifier reported by user device 612 todetermine the position of user device 612 within the building. Buildingmanagement system 610 may send the position of user device 612 tocontrol device 214. Building management system 610 may select a userinterface for monitoring and/or controlling the building zone in whichuser device 612 is currently located or a building zone in which userdevice 612 has been located previously.

Still referring to FIG. 9, building management system 610 is shownproviding the selected user interface to application gateway 910 (step914), which provides the selected user interface to user device 612(step 916). In other embodiments, BMS controller 12 may provide theselected user interface directly to user device 612. User device 612 maypresent the selected user interface on a user interface of user device612. The use interface may be, for example, an electronic display orother user interface element of user device 612. Advantageously,building management system 610 may automatically detect the location ofuser device 612 and deliver a location-specific user interface to userdevice 612 without requiring a user to input location information.

Referring now to FIG. 10, a floorplan 1000 of a home and/or building isshown. The home is shown to include several different zones (e.g., roomsor areas) including a living room, a first bedroom, a second bedroom, abathroom, a kitchen, and a dining room. A control device 214 may beinstalled in one of the rooms or zones. For example, FIG. 10 shows amain control unit (e.g., control device 214) installed in the livingroom. The main control unit may serve as a central hub for monitoringenvironmental conditions, controlling various devices throughout thehome, and/or tracking occupancy through multiple rooms and/or zones ofthe home.

Sensor units 1002 (e.g., proximity sensor 520, remote camera 506,occupancy sensor 516, routers 804-808, emitter 902, etc.) may beinstalled in various rooms or zones in the home. For example, FIG. 10shows a sensor unit installed in each of the bedrooms, the bathroom, thekitchen, and the dining room. In some embodiments, the sensor units 1002measure signals strengths between user devices (e.g., user device 612).In various embodiments, sensor units 1002 are configured to relay imagedata and/or audio data to control device 214. Control device 214 mayidentify occupants based on the image and/or audio data. The measuredsignal strengths may be used to determine the occupancy of the owner ofthe user device.

In some embodiments, a building management system and/or control device214 determines the location of the user device. The sensor units 1002may be configured to measure environmental conditions within each roomor zone and to receive user input (e.g., voice commands via amicrophone). For example, each sensor unit 1002 may include a pluralityof sensors (e.g., a temperature sensor, a humidity sensor, a smokedetector, a light sensor, a camera, a motion sensor etc.) configured tomeasure variables such as temperature, humidity, light, etc. in the roomor zone in which the sensor unit is installed. The sensor units 1002 maycommunicate (e.g., wirelessly or via a wired communications link) withthe control device 214 and/or with each other. In some embodiments,sensors, such as low power door sensors, can communicate with repeatersdisposed in the gang boxes or other locations using a low power overheadprotocol. The repeaters can provide wired or wireless communication tothe main control unit.

Referring now to FIG. 11, a diagram of control device 214 receivingoccupancy information is shown, according to an exemplary embodiment. Insome embodiments, control device 214 is configured to receive occupancydata 1102 from sensors 714. In some embodiments, sensors 714 are atleast one or a combination of camera 724, microphone 726, a motionsensor (e.g., proximity sensor 722), and/or any other occupancy sensor.In some embodiments, occupancy module 754 may be configured to processthe occupancy data to determine the identity of any detected occupants.

In some embodiments, occupancy module 754 may be configured to determinethe identity of an occupant based on occupancy data 1102 received fromsensors 714. In some embodiments, the occupancy module 754 receivessensor input from sensors 714 where the sensors may include camera 724.Occupancy module 754 can perform digital image processing to identifythe one or more users based on the digital images received from camera724. In some embodiments, digital image processing is used to identifythe faces of the one or more users, the height of the one or more users,or any other physical characteristic of the one or more users. In someembodiments, the digital image processing is performed by image analysistools such as edge detectors and neural networks. In some embodiments,the digital image processing compares the physical characteristics ofthe one or more users with physical characteristics of previouslyidentified users.

In some embodiments, the occupancy module 754 receives sensor input frommicrophone 726. Microphone 726 can be any of a plurality of microphonetypes. The microphone types include, for example, a dynamic microphone,a ribbon microphone, a carbon microphone, a piezoelectric microphone, afiber optic microphone, a laser microphone, a liquid microphone, and anaudio speaker used as a microphone. In some embodiments, the occupancycontroller analyzes the audio data received from the microphone. In someembodiments, the occupancy controller 636 identifies one or more usersbased on voice biometrics of the audio received from microphone 726.Voice biometrics are the unique characteristics of a speaker's voice.Voice biometrics include voice pitch or speaking style that result fromthe anatomy of the speaker's throat and/or mouth. In some embodiments,the occupancy module 754 uses a text dependent voice recognitiontechnique. In some embodiments, the occupancy module 754 uses a textindependent voice recognition technique to identify the one or moreusers. Occupancy module 754 may be configured to store voice biometricslinked to individuals. Occupancy module 754 may be configured to matchthe stored voice biometrics to voice biometrics determined foroccupants.

In some embodiments, the occupancy module 754 uses the text dependentvoice recognition technique to identify the one or more users based on apassword or particular phrase spoken by one of the users. For example,the user may speak a phrase such as “This is Felix, I am home.” Theoccupancy module 754 can perform speech recognition to determine thespoken phrase “This is Felix, I am home” from the audio data receivedform the microphone. In some embodiments, occupancy module 754 uses oneor a combination of a hidden Markov models, dynamic time warping, and aneural networks to determine the spoken phrase. Occupancy module 754compares the determined spoken phrase to phrases linked to users. If thephrase, “This is Felix, I am home” matches a phrase linked to a userFelix, the occupancy controller identifies the user as Felix.

In some embodiments, occupancy module 754 uses the text independentvoice recognition technique to identify one or more users based onparticular voice biometrics of the user. The text independent voicerecognition technique performs a pattern recognition technique toidentify the particular voice biometrics of the speaker from the audiodata received from the microphone. The voice biometrics include voicepitch and speaking style. In some embodiments, a plurality of techniquesare used to identify the voice biometrics of the user. The techniquesinclude frequency estimation, hidden Markov models, Gaussian mixturemodels, pattern matching algorithms, neural networks, matrixrepresentation, Vector Quantization, and decision trees.

In some embodiments, the occupancy module 754 is configured to captureaudio data from one or more users and perform pre-processing. In someembodiments pre-processing may be compressing the audio data, convertingthe audio data into an appropriate format, and any other pre-processingaction necessary. The occupancy module 754 may be configured to transmitthe captured spoken audio data to a voice recognition server viacommunications interface 732 and network 602 as described with referenceto FIGS. 6-7. The voice recognition server (e.g., building managementsystem 610) may be configured to determine the identity of the occupantand transmit the identity of the occupant to occupancy module 754.

Still referring to FIG. 11, control device 214 is configured to receiveoccupancy information 1104 from building management system 610. In someembodiments, building management system 610 may be configured todetermine the location of a user based on trilateration methods asdescribed with reference to FIG. 8. In various embodiments, buildingmanagement system 610 may be configured to determine the location of auser based on signal strength to an emitter as described with referenceto FIG. 9.

The building management system 610 may send the identity of the occupantand the location of the occupant in a building (e.g., building 10). Insome embodiments, control device 214 is configured to cause zones and/orbuildings to be controlled to environmental conditions (e.g.,temperature setpoint, humidity setpoint, etc.) based on environmentalcondition preferences and location of the occupant. The control device214 may be configured to generate control signals for HVAC equipment 738to achieve the preferred environmental conditions. In variousembodiments, the control device 214 may be configured to play music indifferent zones and/or cause a music platform (e.g., Pandora, Spotify,etc.) to play music preferences of the identified user in the zoneand/or building which the user is located.

Referring now to FIGS. 12-13, a diagram 1200 and flowchart 1300illustrating a process for controlling a building zone based on detectedoccupancy is shown, according to an exemplary embodiment. In someembodiments, the process is performed by occupancy module 754, asdescribed with reference to FIG. 7. Control device 214 may identify auser and load user-specific climate control settings for the identifieduser (step 1302). In some embodiments, control device 214 identifies theuser by communicating with a portable device carried by the user (e.g.,a phone, a RFID card, a NFC tag, etc.) In other embodiments, the user isidentified by voice (FIG. 11), by appearance (FIG. 11), trilateration ofwireless signals from a user device (FIG. 8), communicating withwireless emitters via a user device (FIG. 9) or any other data collectedby sensors in zones 1202 and 1204. Control device 214 may determine thatthe user is located within a first zone 1202 of a home or building (step1304) and may operate home/building equipment to achieve theuser-specific climate control settings in the first zone 1202 (step1306). Control device 214 may turn the lights on in zone 1202 (step1308). In some embodiments, the lights are dimmed to user specifiedlevels. Control device 214 may be configured to operating music playedin zones 1202 when the user is identified (step 1310). In someembodiments, the user is linked to specific songs, playlists, and/orvolumes. Control device 214 may be configured to cause audio systems toplay certain playlists and/or radios in zone 1202 when the user isidentified in zone 1202.

Control device 214 may determine that the user has moved to a secondzone 1204 of the home/building (step 1308) and may operate thehome/building equipment to achieve the user-specific climate controlsettings in the second zone 1204 (step 1310). In some embodiments,control device 214 is configured to operate the lighting of zones 1202and 1204 based upon the location of the user (step 1312). For example,control device 214 may turn off lights in zone 1202 and on in zone 1204when the user moves from zone 1202 to zone 1204 (step 1316). Controldevice 214 may be configured to operating music played in zones 1202 and1204 when the user moves from zone 1202 to 1204 (step 1316). Forexample, when the user moves to zone 1204, the music may stop playing inzone 1202 and being playing in 1204 (step 1318).

Referring now to FIG. 14A, a flowchart 1400 illustrating a buildingcontrol process which may be performed by occupancy module 754 ofcontrol device 214 as described with reference to FIG. 7, according toan exemplary embodiments. In some embodiments, control device 214 isconfigured to determine the location and identity of a user based onwireless communication (step 1402) with user device 612 when user device612 is associated with the user. In some embodiments, wirelesstriangulation is used to determine the location of the user based onsignal strengths between user device 612 and routers and/or emitters asdescribed with reference to FIGS. 8-9.

In some embodiments, a unique device identifier (e.g., a serial number,a hardware ID, a MAC address, etc.) may link user device 612 to aparticular user profile. When user device 612 is determined to be in thebuilding (e.g., building 10) the user may receive a command toauthenticate (i.e., log in) with building management system 610 via userdevice 612 (step 1404). In some embodiments, user device 612automatically authenticated with the building management system 610based on a unique device identifier. In some embodiments, theauthentication is performed directly between the user device and thebuilding management system 610. In various embodiments, control device214 receives the unique device identifier from the user device andfacilitates the authentication with building management system 610. Invarious embodiments, the user may be prompted to enter a user name andpassword via user device 612 and/or user interface 702 of control device214 to authenticate with the building management system 610.

In some embodiments, the building management system 610 may beconfigured to generate a three dimensional building map with thelocation and identity of multiple building occupants located on the map(step 1406). The building map may contain multiple floors, zones,buildings, and/or campuses. In some embodiments, the three dimensionalbuilding map may be accessible via a user device (e.g., user device 612)if the user device has the proper permissions to view the building map.In some embodiments, the user device must be associated with atechnician, and/or any other building employee for the user to haveaccess to the three dimensional building map.

In some embodiments, building management system 610 keeps a record ofvarious occupants of the building and associated permissions with eachoccupant. In some embodiments, the permissions are music permission(i.e., if the user can change music, radio stations, volume, etc. of themusic played in various zones of the building). In some embodiments, thepermissions allow a user to change music, radio stations, music volume,environmental setpoints, lighting and/or any other adjustable setting ofcontrol device 214 via user interface 702, microphone 726, and/or userdevice 612 associated with the user. In some embodiments, thepermissions to change and/or adjust environmental conditions (e.g.,temperature setpoint, humidity setpoint, etc.) (step 1408). Based on thepermissions and user preferences, the building management system 610 maybe configured to send commands to the devices (e.g., control device 214)to adjust environmental zone conditions, lighting, and music of zones(step 1410).

Referring now to FIG. 14B, table 1412 of occupant permissions andpreferences is shown, according to an exemplary embodiment. In someembodiments, the table may be permissions and preferences which controldevice 214 receives from building management system 610 as describedwith reference to FIG. 11 and/or FIG. 14A. In some embodiments, table412 contains permissions and preferences for occupant A 1414, occupant B1416, and occupant C 1418. Permissions and preferences for any number ofoccupants may be received from building management system 610 and/orstored on control device 214. Occupant A 1414, occupant B 1416, andoccupant C 1418 may have preferred preferences such as preferredsetpoint 1420, music 1422, lighting 1424, and shades/blinds 1426.Occupant A 1414, occupant B 1416, and occupant C 1418 may havepermissions to change and/or operate certain features of control device214 (i.e., setpoints, music, lighting, etc.) Any number of permissionsand/or preferences may be received from building management system 610for occupant A 1414, occupant B 1416, and occupant C 1418.

Occupant A 1414 has a preferred setpoint of 78 degrees F., occupant B1416 has a preferred setpoint of 75 degrees F. and occupant C 1418 hasno permission to change the setpoint. In some embodiments, when anoccupant with a preferred setpoint moves from a first zone to a secondzone, the preferred setpoint may follow the occupant and the second zonemay be heated and/or cooled to the preferred setpoint. An occupant withno permission to change a setpoint (e.g., occupant C 1418) may not beable to make any changes to the setpoint.

In some embodiments, control device 214 may disable changes to thesetpoint whenever occupant C 1418 is determined to be a set distancesfrom control device 214. In some embodiments, control device 214 maydisable changes to the lighting whenever occupant C 1418 is identifiedin the zone that control device 214 is located. In some embodiments,when occupant C 1418 is authenticated and/or logged in with the buildingmanagement system and/or control device 214 as described with referenceto FIG. 14A, occupant C 1418 may be notified via a user device (e.g.,user device 612) that occupant C 1418 is unable to change the setpoint.In some embodiments, occupant C 1418 is notified via the user interface702 (e.g., through images on electronic display 706, audio from speakers710, etc.) that occupant C 1418 does not have permission to adjust thesetpoint.

Occupant A 1414, occupant B 1416, and occupant C 1418 may havepermissions and preferences for music 1422 such as the music played inzones of a building (e.g., building 10). In table 1412, occupant A 1414has a preference for no music, occupant B 1416 has a preferred radiostation, and occupant C 1418 does not have permission to play music. Insome embodiments, whenever occupant B 1416 is in a zone, the buildingequipment in that zone may automatically play radio station AM 1130. Insome embodiments, when occupant A 1414 enters a zone, the buildingequipment in that zone will automatically turn off any music that isplaying. In some embodiments, any attempt by occupant C 1418 to playmusic and/or audio will be met by a notification that occupant C 1418does not have the appropriate permissions to change the music and/oraudio.

In some embodiments, control device 214 may disable changes to musicpreferences whenever occupant C 1418 is determined to be a set distancesfrom control device 214. In some embodiments, control device 214 maydisable changes to the lighting whenever occupant C 1418 is identifiedin the zone that control device 214 is located. In some embodiments,when occupant C 1418 is authenticated and/or logged in with buildingmanagement system 610 and/or control device 214 via a user device (e.g.,user device 612) as described with reference to FIG. 14B, occupant C1418 may be notified via a user device (e.g., user device 612) thatoccupant C 1418 is unable to change the music preferences. In someembodiments, occupant C 1418 is notified via the user interface 702(e.g., through images on electronic display 706, audio from speakers710, etc.) that occupant C 1418 does not have permission to adjust themusic preferences.

Occupant A 1414, occupant B 1416, and occupant C 1418 may havepermissions and preferences for lighting 1424. In some embodiments, thelighting in zones and/or a building (e.g., building 10) may be adjustedbased on permissions and preferences of occupant A 1414, occupant B1416, and occupant C 1418. Occupant A 1414 may have no permission tochange lighting. Occupant B 1416 may have a preference for lighting inthe zone which occupant B occupies to be dim. Occupant C 1418 may havethe preference that the lighting associated with the zone which occupantC 1418 occupies be at full brightness.

In some embodiments, control device 214 may disable changes to thelighting whenever occupant A 1414 is determined to be a set distancesfrom control device 214. In some embodiments, control device 214 maydisable changes to the lighting whenever occupant A 1414 is identifiedin the zone that control device 214 is located. In some embodiments,when occupant A 1414 is authenticated and/or logged in with buildingmanagement system 610 and/or control device 214 via a user device (e.g.,user device 612) as described with reference to FIG. 14A, occupant A1414 may not have the ability to change the lighting settings of controldevice 214 and may be notified via a user device (e.g., user device 612)that occupant A 1414 is unable to change the lighting settings. In someembodiments, occupant A 1414 is notified via the user interface 702(e.g., through images on electronic display 706, audio from speakers710, etc.) that occupant A 1414 does not have permission to adjust thelighting settings.

Occupant A 1414, occupant B 1416, and occupant C 1418 may havepermissions and preferences for shades/blinds 1426. In some embodiments,occupant A 1414 has the preference that natural light be used toilluminate the zone which occupant A 1414 occupies whenever possible.Using natural light may include opening shades, opening blinds, and/oropening shutters. Occupant B 1416 and occupant C 1418 may have nopermission to open and/or close shades, blinds, and/or shutters. Anyattempt by occupant B 1416 and occupant C 1418 to open and/or closeshades, blinds, and/or shutters controlled by control device 214 may bemet with a notification that occupants A 1416 and/or occupant C 1418 maynot have the proper permission to open and/or close the shades, blinds,and/or shutters.

In some embodiments, control device 214 may disable changes to theshades and/or blinds whenever occupants B 1416 and/or occupant C 1418are determined to be a set distance from control device 214. In someembodiments, control device 214 may disable changes to the shades and/orblinds whenever occupant B 1416 and/or occupant C 1418 are identified inthe zone which control device 214 is located. In some embodiments, whenoccupant B 1416 and/or occupant C 1418 are authenticated with buildingmanagement system 610 and/or control device 214 via a user device (e.g.,user device 612) as described with reference to FIG. 14A, occupants B1416 and/or occupant C 1418 may be notified via a user device (e.g.,user device 612) that occupants B 1416 and/or occupant C 1418 are unableto change the shades and/or blinds. In some embodiments, occupant B 1416and/or occupant C 1418 are notified via the user interface 702 (e.g.,through images on electronic display 706, audio from speakers 710, etc.)that occupants B 1416 and/or occupant C 1418 do not have permission toadjust the shades and/or blinds.

Display and Emergency Features

Referring now to FIGS. 15 and 16A, a diagram 1500 and flowchart 1600illustrating a control process which may be performed by emergencymodule 756 and/or building module 746, according to some embodiments.Control device 214 may receive a weather forecast 1502 from a weatherserver 608 (step 1602) and display the weather forecast 1502 via userinterface 702 of control device 214 (step 1604). Control device 214 mayilluminate ambient lighting 1512 of control device 214 in response tothe weather forecast 1502 indicating a weather-related warning (step1606). In some embodiments, audio 1514 may be generated when the weatherforecast 1502 indicates a weather-related warning. The audio can be asiren, a warning message, and/or any other emergency related audio.Control device 214 may determine an adjustment to a control signal 1510for HVAC equipment 738 based on the weather forecast (step 1608).Control device 214 may generate and provide an adjusted control signal1510 to HVAC equipment 738. In some embodiments, the control signal 1510may cause shutters and/or doors to automatically close. The controlsignal 1510 may cause building sirens (e.g., speakers 504) to playemergency related audio (e.g., “Please evacuate the building”, “Takeshelter away from windows”, etc.)

Referring now to FIG. 16B, a flowchart of process 1612 illustrating thepropriety of message data streams is shown, according to an exemplaryembodiment. In some embodiments, process 1612 may be operated by controldevice 214 as described with reference to FIG. 7. In step 1614, controldevice 214 receives messages (e.g., general messages, emergencymessages, etc.) based on a data stream from the building managementsystem (e.g., building management system 610). Control device 214 may beconfigured to display general messaging (e.g., zone temperatures,building events, etc.) and/or emergency information on user interface702 based on a data stream received from building management system 610.

In some embodiments, if a connection is lost between control device 214and building management system 610, control device 214 may displaymessages stored and/or generated locally on control device 214 (step1616) on user interface 702. In some embodiments, the display messagesstored and/or generated locally on control device 214 include zonetemperatures, zone humidity, building events, etc. In the event that anemergency is detected by emergency sensors (e.g., building emergencysensor(s) 606) connected to control device 214, the general messagesreceived from building management system 610 may be overridden andemergency messages may be display on user interface 702 based on datareceived from the emergency sensors (step 1618). In some embodiments,when the data received from the emergency sensors is above a predefinedthreshold and/or below another predefined threshold, an emergency may beidentified. In the event that an emergency is detected by emergencysensors (e.g., building emergency sensor(s) 606) connected to controldevice 214, the general messages stored locally and/or determined bycontrol device 214 may be overridden and emergency messages may bedisplay on user interface 702 based on data received from the emergencysensors.

In some embodiments, control device 214 may receive a message from aweather server (e.g., weather server 608). Control device 214 may beconfigured to override general messages received from buildingmanagement system 610 when a notification for weather related emergencyand/or any other type of emergency is received from weather server 608(step 1620). Control device 214 may be configured to display weatherrelated emergency notifications and directions via user interface 702over the general messages received from building management system 610.

Referring now to FIG. 17, a drawing of a device displaying an emergencyscreen 1700 during an emergency situation is shown, according to anexemplary embodiment. In some embodiments, emergency screen 1700 may bedisplayed by control device 214. Emergency screen 1700 is shown toinclude an alert title 1702, an alert icon 1704, instructions 1706,directions 1708, and menu option 1710.

Emergency screen 1700 is shown to have an alert title 1702 describingthe contents of the page. In this exemplary embodiment, the title is“TORNADO WARNING.” In some embodiments, alert title 1702 is customizableto provide more information. In other embodiments, alert title 1702 iscustomizable to provide less information. Alert title 1702 may be abutton which takes the user to a page related to the title. For example,clicking alert title 1702 may take a user to a menu of pages related to“TORNADO WARNING.” In some embodiments, clicking and/or pressing alerttitle 1702 navigates to a website and/or other entity. The website maybe a weather server and may provide more information into the nature ofthe emergency.

Emergency screen 1700 is also shown to have an alert icon 1704. In thisexemplary embodiment, alert icon 1704 is an image of a tornado. Alerticon 1704 may be any symbol, text, etc., and indicates the nature of thealert. For example, alert icon 1704 may be an image of a snowflake, textreading “FLOOD,” text reading “FIRE,” text reading “ACTIVE SHOOTER,”etc. Alert icon 1704 provides information to a user about the alert, andmay be any indicator relating to any type of emergency.

Emergency screen 1700 is shown to have instructions 1706. Instructions1706 can provide information to a user about how to proceed in thecurrent situation. In some embodiments, instructions 1706 may inform auser of how to exit a building. For example, instructions 1706 mayinform a user of which room to head to. In other embodiments,instructions 1706 inform a user of which authorities to inform, etc. Forexample, instructions 1706 may instruct a user to call an ambulance,then the police, then building and/or campus security. Instructions 1706may be downloaded from a network (e.g., network 602). In someembodiments, instructions are requested from network 602. In variousembodiments, instructions are pushed to control device 214. Instructions1706 may be stored for access by control device 214 in specificsituations. In some embodiments, instructions 1706 may be stored locallyon control device 214. In other embodiments, instructions 1706 may bestored remotely from control device 214. Instructions 1706 may be storedanywhere and retrieved by control device 214.

Emergency screen 1700 is also shown to have directions 1708. In someembodiments, directions 1708 may be an embodiment of instructions 1706.In other embodiments, directions 1708 provide different information frominstructions 1706. Directions 1708 may provide a user informationregarding where to go. For example, directions 1708 may be an arrowpointing in the correct direction to go. In some embodiments, controldevice 214 is portable, and may detect movement to alter directions1708. For example, directions 1708 may change depending on the directiona user is facing. Directions 1708 may be any indicator providingdirectional information, and is not limited to those specificallyenumerated.

Emergency screen 1700 is also shown to have a menu option 1710. In thisexemplary embodiment, option 1710 is an “Ok” button. For example, option1710 may accept the prompt. In some embodiments, option 1710 may simplydismiss the prompt. In other embodiments, option 1710 may proceed to thenext action. In some embodiments, option 1710 is a forward button, amenu, etc. Option 1710 may perform any function, and is not limited tothose specifically enumerated.

Referring now to FIG. 18, an emergency screen 1800 of an evacuationroute is shown, according to an exemplary embodiment. In someembodiments, emergency screen 1800 is displayed by control device 214.Screen 1800 is shown to include position indicator 1802, floorplan 1804,and directions 1806. Screen 1800 may include other elements andcomponents, and is not limited to those specifically enumerated.

Screen 1800 is shown to include position indicator 1802. Positionindicator 1802 may provide information on the whereabouts of a user, oranother person, item, component, etc. For example, in this exemplaryembodiment, position indicator 1802 is shown as an image of a person,and indicates the position of the person. In some embodiments, positionindicator 1802 may indicate the position of multiple users, items, etc.Position indicator 1802 may further include a differentiating label,which may indicate which user, item, etc. is shown by each of themultiple indicators. In other embodiments, position indicator 1802 mayindicate the position of a single user, item, etc. Position indicator1802 may be any symbol, text, etc., and is not limited to thosespecifically enumerated.

Screen 1800 is shown to include floorplan 1804. Floorplan 1804 may be adiagram of a floorplan of an area serviced by control device 214. Insome embodiments, the area is the area in which control device 214 isinstalled. In other embodiments, the area is another area, and may beselected by a user. In some embodiments, floorplan 1804 may showmultiple locations. For example, floorplan 1804 may show both floors ofa two-story building. A user may be able to select multiple locations todisplay (e.g., the top floor and the fourth floor of a 35 storybuilding). In other embodiments, floorplan 1804 may show a singlelocation. Floorplan 1804 may display any number of any locations, and isnot limited to those specifically enumerated.

Screen 1800 is also shown to include directions 1806. Directions 1803may provide information to a user regarding how to navigate to a certainlocation (i.e., evacuate). In some embodiments, directions 1806 providethe fastest route out of a building. For example, directions 1806 maydirect a user to the exit of a building in case of an emergency. Inother embodiments, directions 1806 provide a user with a route to aspecified location. For example, directions 1806 may direct a user to ashelter (e.g., a basement fallout shelter, a safe location with nowindows, etc.) In yet other embodiments, directions 1806 may allow auser to select options for the route. For example, a user may be able toindicate that she wishes to stay on the same floor, avoid stairs, etc.In yet other embodiments, directions 1806 may enable a user to selectmultiple destinations. For example, a user may indicate that he wishesto stop by a supply room before continuing to a conference room. Theuser may be able to make edits to any selections made. Directions 1806are not limited to those forms and features specifically enumerated.

Referring now to FIGS. 19-20, a diagram 1900 and flowchart 2000illustrating a control process which may be performed by voice controlmodule 748 is shown, according to an exemplary embodiment. In someembodiments, flowchart 2000 is performed by voice command module 744.Control device 214 may receive a voice command 1904 from a user 1902(step 2002) via a microphone (e.g., microphone 726) and may determinethat the voice command 1904 contains a request to compile a grocery list(step 2004). In some embodiments, the voice command 1904 may be aconcierge question as described with reference to FIGS. 30-32. Controldevice 214 may compile a grocery list 1906 based on the voice command1904 received from the user 4102 (step 4156). In some embodiments,control device 214 replies to a concierge questions via a speaker (e.g.,speaker 710). In some embodiments, control device 214 is configured tosend a grocery order 1908 to a grocery service 1910 (step 2008) andreceive an order confirmation 1912 from the grocery service 1910 (step2010). Control device 214 may provide an audio feedback 1914 indicatingthat the grocery list has been updated and/or that the grocery order hasbeen placed. In various embodiments, the grocery list can be updatedand/or an order can be placed through touch based input. In someembodiments, the steps of flowchart 2000 can be performed by touchingbuttons on a touch screen associated with control device 214.

Health Care and Hospital Features

Referring now to FIG. 21, control device 214 is shown to communicate tovarious health care devices and systems, according to an exemplaryembodiment. In some embodiments, healthcare module 752 facilitateshealthcare functions of control device 214. Control device 214 shown tointeract with healthcare sensors 604, user device 612, buildingmanagement system 610, medical server 2102 and network 602. In someembodiments, control device 214 communicates with healthcare equipment2104. In various embodiments, the healthcare module 752 communicateswith healthcare equipment 2104 directly and/or via network 602. In someembodiments, healthcare equipment 2104 is shown to include life supportdevices 2106, hospital/clinic devices 2108, home medical devices 2110,or implantable medical devices 2112 (e.g., pacemakers, cardioverterdefibrillators, etc.).

Healthcare module 752 facilitates healthcare functionality of controldevice 214. Functions performed by healthcare module 752 may includemonitoring the health of occupants of the area in which control device468 is installed. In some embodiments, healthcare module 752 may monitoran occupant's health through data collected by healthcare sensors 604and/or may determine a health metric for the occupant based on the datacollect by healthcare sensors 604. For example, healthcare module 752may monitor an individual's health by tracking his temperature throughhealthcare sensor 604. In some embodiments, healthcare sensor 604 is oneor more or a combination of a smartwatch, a smart wrist band, a heartrate monitor, a pacemaker, a portable insulin device, and/or any otherwearable medical device. In some embodiments, healthcare sensor 604 is acamera, an infrared camera, and/or any other occupancy detection device.Healthcare module 752 may use healthcare sensors 604 to monitor a user'swaking/rest times, heart rate, insulin levels, body temperature, etc.Healthcare module 752 is not limited to monitoring the health attributesspecifically enumerated, and may monitor any aspect of a user'sbio-status. In some embodiments, control device 214 is configured toforward any data collected by healthcare sensors 604 and/or healthcareequipment 2104 to medical server 2102. In some embodiments, medialserver 2102 is a hospital server, a nurses station computing system,and/or an emergency response operator server.

Healthcare module 752 may communicate with user interface 702 or userdevice 612 belonging to a user to sense and collect health data. Forexample, healthcare module 752 may communicate with an individual'ssmartwatch which contains a heart rate monitor to track the individual'sheart rate. In some embodiments, control device 214 does not communicatewith healthcare sensors 604 which monitor a user's health, and insteadcollects data solely from healthcare equipment 2104. In otherembodiments, control device 214 contains sensors and collects data fromother devices, combining the data collected to produce a general metricof a user's health.

Healthcare module 752 may detect a change of a predetermined amount or asensor value over or under a predetermined threshold value (e.g.,abnormally high and/or low heart rate (i.e., bradycardia andtachycardia), abnormally high and/or low insulin level, abnormally highand/or low temperature, etc.). In some embodiments, healthcare module752 may monitor the heart rate of an occupant and determine if the heartrate is abnormal (i.e., arrhythmia). In some embodiments, healthcaremodule 752 may alert a user, the monitored occupant, a nurse's stationcomputing system, a hospital server, a hospital computing system, call911 (i.e., send a message to an emergency response server and/or anemergency response computing system) etc. For example, healthcare module752 may communicate with user device 612 of a user to display an alertdescribing the situation triggering the healthcare alert. Healthcaremodule 752 may communicate with network 602 to update a healthcaresystem (e.g., medial server 2102) with new data collected, set a flag ona user's condition, etc. For example, healthcare module 752 may senddata to a patient database and update a value for a body temperature,blood pressure, etc.

In some embodiments, a heart rate and/or body temperature is measured bya smart wrist band and/or smart watch (e.g., healthcare sensors 604).The heart rate and/or body temperature (e.g., health data 2103) may besent to control device 214. In some embodiments, healthcare sensors 604are cameras. The cameras may be heat sensitive. The heat images (e.g.,health data 2103) may be sent to control device 214. Control device 214may determine the body temperature of various occupants of a building(e.g., building 10) based on the heat images (e.g., health data 2103)received form healthcare sensors 604.

Healthcare module 752 may send push alerts to user device 612 fromnetwork 602. For example, network 602 may receive a notification that itis time for a middle school individual to take her medication. Controldevice 214 may communicate with user device 612 of the individual, ateacher, a nurse, etc. to alert the user of user device 612 that it istime for the individual to take her medication. In some embodiments,control device 214 may communicate with a user through user interface702 to convey healthcare information. For example, network 602 mayreceive a notification that it is time for an individual's appointmentwith the nurse. Network 602 may communicate with control device 214 toconvey the information to the nurse, the individual, the individual'scurrent teacher, etc. For example, control device 214 may have access toa user's schedule and/or calendar, and adjust actions accordingly. Insome embodiments, control device 214 may determine that an individual iscurrently in math class, and may send an alert to user device 612 of theindividual. In other embodiments, control device 214 may determine thatan individual is currently in a free period with a specific teacher in aspecific room, and may send an alert to a control device 214 installedin the room, or to a user device 612 of the teacher. Control device 214may convey healthcare information through any media, and is not limitedto those specifically discussed.

Healthcare module 752 may contain some or all of the features ofoccupancy module 754. The occupancy detectors (e.g., healthcare sensors604, sensors 714, etc.) may be installed in a patient room in a healthcare facility and may be used to monitor the presence of the patient inthe room. Healthcare module 752 may communicate with the network 602,medical server 2102, and/or building management system 610 to alertmedical personnel if a patient leaves their room without permission.Healthcare module 752 may communicate with a user interface to determinethe identities of persons in a patient's room. For example, theoccupancy detector may use a camera and facial recognition software todetermine the identities of medical personnel that are present.Healthcare module 752 may use camera and facial recognition to determinethe presence of visitors and other unauthorized personnel in a patient'sroom.

In some embodiments, the healthcare module 752 communicates with usersor relevant persons when an emergency situation arises (e.g., buildingmanagement system 610, medical server 2102, user device 612, etc.)Healthcare module 752 may receive the patient's health information fromthe network, healthcare sensors 604, and/or healthcare equipment 2104,and display it to medical personnel if a medical alert is detected(e.g., abnormal blood pressure, abnormal oxygen saturation, abnormalheart rate, abnormal heart rhythm, etc.). In another embodiment,healthcare module 752 may communicate to the patient or to medicalpersonnel when a regular medical procedure is scheduled. For example,healthcare module 752 may communicate to the patient or to medicalpersonnel when a pill is to be taken, when an IV is to be replaced, whena wound dressing is to be changed, etc. In another embodiment,healthcare module 752 may communicate with alert module to communicatewith user device 612 of a patient. For example, if a patient isundergoing treatment requiring regular pill taking may receive alertsfrom an alert module on a mobile device (e.g., a smartphone, smartwatch, wearable, laptop, etc.).

Healthcare module 752 may communicate with any systems, devices, etc.connected to control device 214. For example, healthcare module 752 mayissue an alert to medical personnel which is pushed to control device214 (e.g., a nurse's station) and mobile devices (e.g., user device 612of medical personnel assigned to the patient, etc.) Healthcare module752 may issue an alert which is pushed to user devices 612 throughnetwork 602. Healthcare module 752 may be in communication with allmodules of control device 214.

In some embodiments, healthcare module 752 may require the credentialsof healthcare personnel to make changes related to treatment of thepatient. The healthcare module 752 may record the unique identity of anyuser making changes to a patient's treatment.

Referring now to FIGS. 22 and 23, drawings of control device 214communicating with other control devices 468 are shown, according toexemplary embodiments. In some embodiments, other control device 214 maybe located locally, such as in another room of the same building. Forexample, referring to FIG. 22, control device 214 is located in apatient's room in a hospital. Control device 214 may communicate withanother control device 214 at a nurse's station in the same hospital.The control device 214 may be directly connected and may communicatedirectly with each other. In another embodiment, the control device 214may be connected via a network.

In various embodiments, other control devices 468 are located remotely,such as in other buildings, states, countries, etc. For example,referring to FIG. 23, control device 214 in a patient's home or anassisted living facility may communicate with control device 214 at ahospital to facilitate out-patient care of the patient. Other controldevices 468 may be located anywhere relative to control device 214, andare not limited to locations specifically discussed or described.

In an exemplary scenario, a patient may be discharged from a medicalcare facility, such as a hospital to their home or to an assisted livingfacility. The patient may, for example, have received a routine checkupor may have been treated for a chronic or acute medical situation. Thepatient may be automatically monitored by healthcare equipment 2104 asdescried with reference to FIG. 21 after being discharged using one ormore control device 214 provided in the patient's home or assistedliving facility. The patient's health may be monitored using implantablemedical devices 2112 or home medical devices 2110 to allow remotemedical personnel to monitor the post care recovery of the patient.Control device 214 may be utilized to facilitate continuing medical care(e.g., physical therapy, medication schedule, follow-up visits to amedical facility, etc.).

Control device 214 may continue to monitor the health of the patientafter receiving medical care. If control device 214 detects a medicalalert, it may take an action, depending on the severity of the medicalalert. For example, control device 214 may prompt the patient to returnto the hospital, alert a local medical person (e.g., an in-home nurse orcaretaker), or may have an ambulance sent to the patient's location.

In some embodiments, control device 214 can transmit patient data to acentral computer system (over a local network or via the internet) incompliance with HIPPA standards and regulations.

In some embodiments, control device 214 may not collect personal healthdata without consent of the person whose data is being collected. Inother embodiments, control device 214 may offer an opt-out system, wherecontrol device 214 is prevented from collecting personal health datawhen a user specifically opts out. In yet other embodiments, controldevice 214 may collect data from all users, and anonymize all databefore storing, analyzing, etc. For example, control device 214 maycollect data from all patients undergoing a particular procedure andanonymize all data before sending to a research facility, hospital, etc.

Control device 214 may collect data from each person, and each person isgiven a window of time to opt-out out retroactively or delete data. Insome embodiments, control device 214 may communicate with the usersthrough the user interface, a mobile device, and/or the network toinform users that their data has been collected. For example, controldevice 214 may push a notification out to all applicable users over thenetwork that his or her information has been collected, and will bestored or sold to a hospital within 24 hours. In some embodiments usersmay be given the full 24 hours to opt-out or delete data. In otherembodiments, users may be given any predetermined period of time inwhich to respond or take action.

Control device 214 may communicate with users to ask for permission toshare his or her information. For example, control device 214 maydisplay a prompt on a mobile device of each person whose data wascollected. In some embodiments, control device 214 may share a user'sdata when permission has been granted. In other embodiments, controldevice 214 may share non-sensitive user data that has been anonymized.

Referring now to FIG. 24, a diagram of scenario 2400 in which controldevice 214 monitors an individual's 2408 health is shown, according tosome embodiments. In part 2402, control device 648 is shown tocommunicate with an individual 2408 via audio, visual items on a screen,a device, etc. The device may be a smartphone, smart watch, fitnesstracker, etc. In other embodiments, the device may be a medical device,such as a pace maker, insulin pump, etc. The device may be any device,and is not limited to those specifically enumerated.

The individual 2408 may communicate directly with control device 214through a user interface, voice commands, etc. For example, individual2408 may tell control device 214 that he does not feel well. In someembodiments, control device 214 may trigger an alert or take some otheraction depending on the information received. In other embodiments,control device 214 may wait for specific instructions to take actionbefore executing any commands.

In part 2404, a screen of control device 214 during normal healthmonitoring operation is shown. Control device 214 has confirmed thatindividual's 2408 body temperature, displays the temperature, theindividual's name, an indication that all is well, and takes no furtheraction. In some embodiments, control device 214 stores the information.In other embodiments, control device 214 sends the information tohealthcare institutions, facilities, professionals (e.g., medical server2102, building management system 610, etc.) Control device 214 mayhandle all information in accordance with HIPAA rules and regulations.

Control device 214 may monitor and collect any health data, such asblood pressure, heart rate, etc. For example, control device 214 maycommunicate with a heart rate monitor, and raise an alarm if anindividual's heart rate becomes irregular, over a threshold rate, etc.For example, control device 214 may detect that an individual isexperiencing a high amount of stress using a combination of bodytemperature and heart rate. Control device 214 is not limited to thehealth statistics specifically enumerated.

In part 2406, control device 214 has automatically detected that ahealth condition has arisen. In this exemplary depiction, the healthcondition is a fever, detected by the high body temperature. In otherembodiments, the health condition may be high stress, arrhythmia, lowblood sugar, etc. Control device 214 may produce a sound, vibrate, flashthe screen, etc. to present an alert to a user. In some embodiments,control device 214 may send a signal to a user device (e.g., user device612, network 602, building management system 610, medical server 2102,etc.) or some other system or device to display the alert, as describedabove.

Referring now to FIG. 25, a drawing of a screen 2500 displayed when anindividual is in distress is shown, according to an exemplaryembodiment. Screen 2500 is shown to include a live feed 2502 of theparticular individual. In some embodiments, live feed 2502 may be a mapor floorplan indicating where the individual is located. In otherembodiments, live feed 2502 may be a still photo of the individual tohelp healthcare professionals locate the individual.

Screen 2500 further includes an alert message 2504 and a cause 2506.Alert message 2504 may display any message, such as “STUDENT COLLAPSE,”“STUDENT EMERGENCY,” etc. In some embodiments, alert message 2504 may becustomized to provide more information, such as the individual's name,emergency contact information, etc. In other embodiments, alert message2504 may be customized to display anything that may be more helpful orappropriate for the environment in which user control device isinstalled. Alert message 2504 is not limited to those messagesspecifically enumerated.

Cause 2506 may be any reason, such as “Cardiac distress,” “Low bloodsugar,” etc. In some embodiments, cause 2506 may be customized toprovide more information, such as the individual's name, emergencycontact information, etc. In other embodiments, cause 2506 may becustomized to display anything that may be more helpful or appropriatefor the environment in which user control device is installed. Cause2506 is not limited to those messages specifically enumerated.

Screen 2500 is further shown to include an icon 2508. Icon 2508 may givea user a quick impression of what the alert is related to. Controldevice 214 is capable of providing alerts for many different categories,such as inclement weather, security, health, etc. Control device 214 isnot limited to those categories specifically enumerated. Icon 2508 maybe a symbol, a word, etc., and may be any indication of what the alertis related to.

Screen 2500 is further shown to include a location 2510. Location 2510may give a user the location of the particular individual to which thealert is related. In some embodiments, location 2510 is provided astext. In other embodiments, location 2510 is provided as a map. Forexample, location 2510 may be displayed as live feed 2502. Location 2510may be displayed or presented to the user in any form, and is notlimited to those specifically enumerated.

Screen 2500 is finally shown to include options 2512, 2514, and 2516.Options 2512, 2514, and 2516 may provide a user with options of actionsto take. In some embodiments, screen 2500 may include more options. Inother embodiments, screen 2500 may include fewer options. The optionspresented may be customized to be more appropriate for each situation.For example, if an individual's insulin pump needs to be restarted,control device 214 may present the option of restarting the pump. Insome embodiments, option 2516 to ignore the alert may not be available.For example, if an individual is in critical condition, such as cardiacarrest, user control device may automatically execute options 2512 and2514 by calling security and 911.

Concierge and Hotel Features

Referring now to FIG. 26A, a diagram of control device 214 is shown foruse in a hotel, according to an exemplary embodiment. In someembodiments, control device 214 receives concierge information frombuilding management system 610. In some embodiments, the conciergeinformation may include local attractions, local restaurants, and/or anyother concierge related information. In some embodiments, hotel module750 is configured to cause control device 214 to send a request forspecific concierge information to building management system 610 vianetwork 602 when a user requests concierge information via userinterface 702 and/or microphone 726. In some embodiments, hotel module750 may cause control device 214 to search for concierge information viathe Internet (e.g., network 602) if the building management system doesnot have the requested concierge information.

In some embodiments, hotel module 750 is configured to process ordersfor food from local restaurants. In some embodiments, control device 214(i.e., hotel module 750) may send a request to a restaurant computingsystem 2602 for a menu. Control device 214 may display the menu to theuser via user interface 702 and may allow the user to order fooddirectly through user interface 702 (i.e., enter orders through userinterface 702). In some embodiments, the user may be able to send areservation request to restaurant computing system 2602 via hotel module750 and display device 702. A user may place an order via user interface702 causing hotel module 750 to communicate with restaurant computingsystem 2602 via network 602. Hotel module 750 may cause payment module758 to process any payment transactions for food orders with financialinstitution system 3504. Payment transactions are described in furtherdetail at FIGS. 35-39.

In some embodiments, hotel module 750 is configured to process requestsfor taxis, busses, subways, trains, and/or planes. In some embodiments,control device 214 communicates with transportation server 2604.Transportation server 2604 may be Uber, Lyft, and/or any other taxiservice. In some embodiments, transportation server 2604 is an airlineserver, a buss server, a train server, etc. Hotel module 750 may allow auser to request a ride from transportation server 2604 and may causepayment module 758 to process payment transactions via network 602 andfinancial institution system 3504. In some embodiments, input device 712may be configured to scan credit and/or debit cards for payment fortransactions with restaurant computing system 2602 and/or transportationserver 2604. In some embodiments, payment module 758 facilitates thetransaction with financial institution system 3504. Input device 712 isdescribed in further detail in FIGS. 35-39.

Referring now to FIG. 26B, a process 2606 for scheduling a stay at ahotel is shown, according to some embodiments. In some embodiments,process 2606 is performed by hotel module 750 of control device 214.Process 2606 may be applied to scheduling any event, and is not limitedto hotels, cruises, etc. Process 2606 begins with step 2608, in which auser provides input to a control device 214. The user may provide inputthrough any means. For example, the user may provide input by voicecommand, tactile input to a user interface (e.g., user interface 702),gesture input, input to a mobile device (e.g., user device 612), etc.

According to this exemplary embodiment, a calendar interface may beprovided to a user via the user interface and/or the mobile device. Insome embodiments, the calendar interface may show the user'sappointments and events. For example, a user's work and personalcalendar events may be displayed on the calendar interface. In otherembodiments, multiple users' schedules may be displayed on the calendarinterface.

The calendar interface may show information such as availabilities for ahotel. In some embodiments, the control device 214 is located inside thehotel which it displays availability for. In some embodiments, thecalendar interface may provide all availabilities. In other embodiments,the calendar interface may be sorted according to room size, amenities,etc. The calendar interface may not be specific to a single hotel. Insome embodiments, the calendar interface may display availabilities formultiple hotels. The hotels shown may be selected by a user. In otherembodiments, control device 214 may automatically select multiple hotelsaccording to criteria such as price range, length of stay, amenities,distance to destinations, hotel ratings, etc.

The information may be displayed in any format. For example, controldevice 214 may display the information as drop-down boxes, check boxes,etc. In some embodiments, control device 214 may display contentdirectly from a hotel's website, a travel website, etc. In otherembodiments, control device 214 may display content parsed from awebsite, in a format native to control device 214.

Process 2606 continues with step 2610, in which a user selects a rangeof days for her stay at the hotel. In some embodiments, a user selects arange of consecutive days. In other embodiments, a user may select a setof non-consecutive days. The user may enter other information, such asbilling information, number of guests, destination, etc. In someembodiments, the calendar interface may display the range of daysselected as darkened days, checked boxes, etc. The information input bythe user is transmitted from control device 214 to a building managementsystem for a hotel (e.g., building management system 610) and/or anyother server for the hotel.

Process 2606 continues with step 2612, the information transmitted fromcontrol device 214 is received by a database. In some embodiments,control device 214 may book a stay at the hotel directly using enteredbilling information. In other embodiments, control device 214 connectsthe user to a travel agent, to the hotel's booking website with thefields pre-populated, etc. The information transmitted from controldevice 214 may be received by any system, and is not limited todatabases. In some embodiments, the database is connected to a hotel'smain system, and hotel staff are notified. In some embodiments, thehotel's main system is building management system 610.

The database may be connected to additional services, such asdestinations, airlines, etc. For example, control device 214 mayautomatically suggest flights from a billing address entered by the userto the destination entered by the user. In some embodiments, controldevice 214 may automatically select flights and present the user with aconfirmation dialog. In other embodiments, control device 214 presents aset of available flights for the scheduled hotel stay. Control device214 may also suggest, book, etc. activities, such as local attractions,tours, ground transportation, etc.

Control device 214 may learn from information entered by the user withhis permission. For example, control device 214 may store informationsuch as a user's preferences for flight times, direct vs. non-directflights, seat preferences, hotel chain preferences, pillow firmnesspreferences, attractions, tours, ground transportation, etc. A user maybe presented with a dialog confirming that she is allowing controldevice 214 to store or analyze such data. In some embodiments, the datais stored remotely. In other embodiments, the data is stored locally oncontrol device 214.

Process 2606 continues with step 2614 in which control device 214provides the user with information. In some embodiments, control device214 provides a confirmation of all bookings made. In other embodiments,control device 214 provides a list of prospective bookings, contactinformation for each option, etc. Control device 214 may provide theuser with any information. In some embodiments, control device 214 maynot provide the user with further information.

In this exemplary embodiment, control device 214 is shown to provide theuser with information through a user interface (e.g., user interface702). In other embodiments, control device 214 may provide the user withinformation through any medium, format, etc. For example, control device214 may provide the user with information through speakers (e.g.,speakers 710), a mobile device (e.g., user device 612), etc.

Referring now to FIG. 27, a process 2700 for arranging transportationvia control device 214 is shown, according to some embodiments. In someembodiments, process 2700 is performed by voice command module 744and/or hotel module 750. Process 2700 begins with step 2702, in which auser is presented with a screen having options for arrangingtransportation. In some embodiments, process 2700 is performedautomatically. In other embodiments, a user may choose to enter atransportation mode to arrange transportation via control device 214.

Process 2700 continues with step 2704, in which control device 214 maypresent the user with a list of available modes of transportation. Forexample, control device 214 may present the user with a list of links todifferent sites of different modes of transportation. In someembodiments, each option is a link which takes the user to a set ofavailable options. Availability may be determined by criteria such asthe current time, the desired time, the location, the distance, the modeof travel, extra considerations for the passenger (oversize luggage,animals, etc.), etc. In some embodiments, the user may enter thecriteria via user interface 702. In various embodiments, the user mayenter the criteria via microphone 726 and voice command module 744.Control device 214 may suggest the closest form of transportation if theselected mode is unavailable. In some embodiments, control device 214may make suggestions and/or arrange the list of modes of transportation(i.e., most relevant mode of transportation to least relevant mode oftransportation) based on the most commonly used, least expensive,fastest, a target destination, etc. For example, if no taxis areavailable at the desired time, control device 214 may suggest taking thesubway.

Process 2700 continues with step 2706, in which control device 214 maymake arrangements for the final selection. For example, once the userhas selected the taxi company, times, options, etc., control device 214may place a call to the company to make arrangements. In someembodiments, control device 214 may enter the information in thecompany's website. In other embodiments, control device 214 may presentthe information to the user, who will make the final arrangementshimself.

Process 2700 continues with step 2708, in which the user is connectedwith her transportation. In some embodiments, the transportation travelsto pick up the user. In other embodiments, the user travels to board thetransportation. The travel arrangements may be made for travelling to adestination, travelling from a destination, etc. Travel arrangements maybe made for any purpose.

Referring now to FIG. 28, drawings of embodiments 2802, 2804, and 2806are shown illustrating options to set arrangement preferences, accordingto some embodiments. Some embodiments are useful in hotel arrangements.In other embodiments, a user may select preferences for anyarrangements, such as travel (e.g., flights, ground transportation,etc.). Embodiment 2802 shows a preferences interface displayed oncontrol device 214. Available options may include guest name,temperature preference, lighting preference, pillow firmness preference,housekeeping preference, etc. Any options may be available for a user toselect, and a user may be able to change her preferences. For example, auser may prefer low lighting in the summer and medium lighting in thewinter. Embodiment 2804 shows a preferences interface displayed on userdevice 612 of a user. Embodiment 2806 shows a preferences interfacedisplayed on a web browser.

Other ways of making arrangements may be available via control device214. In some embodiments, a user may be able to set preferences throughvoice command, gesture input, etc. In other embodiments, a user may setpreferences through specific applications, the hotel's website, etc. Insome embodiments, the control device 214 can send payment and/or creditcard information for the transportation. In some embodiments, hotelmodule 750 may process payment with input device 712 and payment module758.

Referring now to FIG. 29, a process 2900 is shown for preparing a hotelroom for a guest's stay, according to some embodiments. Process 2900begins with step 2902, in which a control device 214 installed in anunoccupied room is in a power-saving state. Control device 214 maydisplay relevant information for the room, such as the room number, thecurrent occupancy, the mode, and the current conditions. Control device214 may display more information. In some embodiments, control device214 may display less information. Control device 214 may be customizedto display the information needed for each situation.

Process 2900 continues with step 2904, in which control device 214receives reservation information for the room at a first time. Controldevice 214 may display a confirmation message. In some embodiments,control device 214 may send a confirmation message to the front desk,main system, etc. In other embodiments, control device 214 may send aconfirmation message to the user. In this exemplary embodiment, thereservation information is received at 1 p.m. local time, and thereservation is for 6 p.m. local time.

Process 2900 continues with step 2906, in which the reservationinformation and/or preferences are analyzed. The received informationmay include room number, temperature, humidity, lighting level, pillowfirmness, etc. Other information and preferences may be set. The formatin which the information is presented to the system, control device 214,etc. may be any format. For example, the system may receive theinformation as raw data while control device 214 receives data parsedinto packets for each category of preference.

Process 2900 continues with step 2908, in which control device 214 maydetermine the amount of time needed to reach the guest's preferredsettings, and when to begin preparing. Control device 214 may determinethe approximate time of arrival of a guest and the approximate amount oftime needed to reach the environmental setpoints of the guest.

Process 2900 continues with step 2910, in which control device 214 hasdetermined the amount of time needed, the time at which to beginpreparing, etc. For example, the preparation for a guest Jimmy arrivingat 6 p.m. is shown to begin at 4 p.m. Control device 214 may begin tochange the temperature, humidity, etc. of the room. For example, controldevice 214 may begin to heat the room from 69° F. to Jimmy's preferred70° F.

Process 2900 continues with step 2912, in which control device 214informs hospitality services of the guest's preferences. In thisexemplary embodiment, Jimmy prefers firm pillows. Control device 214 isshown to inform the front desk of Jimmy's preference. In someembodiments, control device 214 communicates directly with the frontdesk (e.g., a computer at the front desk). In other embodiments, controldevice 214 goes through an intermediary (e.g., network 602) tocommunicate with the front desk. Control device 214 may communicate withthe front desk through any means, and may transmit any information.Control device 214 may be compliant with all privacy rules andregulations.

Process 2900 continues with step 2914, in which control device 214communicates with hotel equipment (e.g., HVAC equipment 738) to achievethe guest's preferences. In this exemplary embodiment, Jimmy prefers lowlighting. Control device 214 may communicate with lights (e.g., HVACEquipment 738) of the room to dim. In some embodiments, control device214 may communicate directly with lights 2920. In other embodiments,control device 214 may communicate through an intermediary, such ashotel automation system (e.g., building management system 610), network602, etc. Control device 214 may communicate with hotel equipment (e.g.,HVAC Equipment 738) through any communications protocol, and is notlimited to those specifically enumerated.

Process 2900 continues with step 2916, in which the guest arrives at theroom at a time indicated by his reservation information transmitted tocontrol device 214. In this exemplary embodiment, Jimmy arrives at Room78 at 6 p.m. local time. Control device 214 is shown to display one ormore room settings. For example, control device 214 is shown to bemounted to a wall of the room, and displays the current roomtemperature—Jimmy's preferred 70° F. Lighting 2920 may be at Jimmy'spreferred low setting. In some embodiments, accommodations such as bedinclination level/mattress firmness (e.g., hotel module 750) may beadjusted. In other embodiments, fewer settings may be adjusted.

Process 2900 continues with step 2918, in which the guest is greeted bycontrol device 214. In some embodiments, control device 214 greets theguest purely visually. For example, control device 214 may display textsaying “Welcome to Room 12, Aaron.” In other embodiments, control device214 may greet the guest using sound. For example, control device 214 maysay “Welcome to Room 78, Jimmy.” Control device 214 may greet the userthrough any means. Control device 214 may be customizable to use agreeting a user has selected, or a greeting specific to the hotel, theroom, etc. the user is staying in. Control device 214 may provideoptions to the user, such as a call for room service, access to thefront desk, concierge, etc. In some embodiments, control device 214performs many of the functions of the concierge desk. In otherembodiments, control device 214 connects a user to the concierge desk.

Referring now to FIG. 30, a process 3000 is shown for communicating witha front desk in the event of a service call. In some embodiments,process 3000 is performed by voice command module 744 and/or hotelmodule 750. In some embodiments, the service call can be made via avoice command and/or through user interface 702. Process 3000 beginswith step 3002, in which a set of options available for a user to make aservice call regarding is shown on control device 214. In someembodiments, the options are displayed through another medium, such as amobile device (e.g., user device 612) of a user. Each option displayedmay be a link. In some embodiments, the link may take the user to a pagewith more information about the option. In other embodiments, the linkmay trigger the service call to be made.

Process 3000 continues with step 3004, in which the user chooses anoption and inputs the selection to control device 214. In someembodiments, the user may provide the input as a voice command. In otherembodiments, the user may provide the selection as a button press, atactile input, a gesture, etc. via a user interface (e.g., userinterface 702). Any input method may be used.

Process 3000 continues with step 3006, in which the selection istransmitted from control device 214 to the appropriate system. In someembodiments, the appropriate system is building management system 610.For example, if the selection made is a request for new towels,housekeeping would be notified. In some embodiments, housekeeping may benotified via building management system 610. In some embodiments,selections made indicate that other departments, such as the front desk,billing, etc. are contacted. In some embodiments, the front desk andbilling are connected to building management system 610.

In other embodiments, the request made can be executed automatically bycontrol device 214. For example, if the user requests that the light beturned off when there are multiple lights in the room, control device214 may use voice command detection (e.g., voice control module 748).Control device 214 may detect which occupancy sensor (e.g., sensors 714)detected the user's voice, or which sensor detected the voice the“loudest.” Control device 214 may decide the location of the user usingan algorithm and turn off the light nearest that location.

Referring now to FIG. 31, a process 3100 is shown for utilizing aconcierge feature of control device 214, according to some embodiments.In some embodiments, process 3100 is performed by voice command module744 and/or hotel module 750. Process 3100 begins with step 3102, inwhich a user asks control device 214 “What time does the gym close?”Control device 214 may access the requested information. In someembodiments, the information is stored remotely from control device 214.In other embodiments, the information is stored locally on controldevice 214. In yet other embodiments, control device 214 may search forthe information, call the front desk, etc.

The user may request information in any way. In some embodiments, theuser may request information through voice commands. In otherembodiments, the user may request information through tactile input(e.g., via user interface 702), via a mobile device (e.g., user device612), etc.

Process 3100 continues with step 3104, in which user control device hasobtained the requested information, and transmits the information to theuser. In some embodiments, control device 214 provides the informationto the user through speakers. For example, control device 214 may say“The gym closes at 12 a.m.” In other embodiments, control device 214 maytransmit the information through text, images, etc. Control device 214may present the information to the user via a user interface (e.g., userinterface 702), a mobile device (e.g., user device 612), etc.

In some embodiments, control device 214 provides information to the userin the same way the user requested the information. For example, if theuser asked a question using a voice command, control device 214 wouldanswer the question via speakers. In other embodiments, control device214 may provide information to the user according to her preferences. Inyet other embodiments, control device 214 would answer the question viaa default method, which may be customizable.

Referring now to FIG. 32, a process 3200 is shown for utilizing aconcierge feature of control device 214, according to another exemplaryembodiment. In some embodiments, process 3200 may be performed by hotelmodule 750 of control device 214 and/or voice command module 744.Process 3200 begins with step 3202, in which a user asks control device214 “What are some local restaurants?” Control device 214 may access therequested information. In some embodiments, the information is storedremotely from control device 214. In other embodiments, the informationis stored remotely on building management system 610. In yet otherembodiments, control device 214 may search for the information on theInternet (e.g., via network 602), call the front desk, etc.

The user may request information in any way. In some embodiments, theuser may request information through voice commands. In otherembodiments, the user may request information through tactile input(e.g., via user interface 702), via a mobile device (e.g., user device612), etc.

Process 3200 continues with step 3204, in which user control device hasobtained the requested information, and transmits the information to theuser. In some embodiments, control device 214 provides the informationto the user through speakers. In other embodiments, control device 214may transmit the information through text, images, etc. if the answer istoo long or too complicated to answer over speakers. For example, if theinformation requested is an explanation for why the sky is blue, usercontrol device may, as a default, present the information to the userthrough text. Control device 214 may present the information to the uservia user interface 702, user device 612, etc.

Referring now to FIG. 33, a process 3300 for requesting accommodationinformation from control device 214 is shown, according to someembodiments. Process 3300 begins with step 3302, in which a userrequests information from control device 214. In some embodiments, theuser may request information via voice command. In other embodiments,the user may request information via a tactile input through userinterface 702, gesture input, etc. Control device 214 may access therequested information. In some embodiments, the information is storedremotely from control device 214. In other embodiments, the informationis stored locally on control device 214. In yet other embodiments,control device 214 may search for the information, call the front desk,etc.

The user may request information in any way. In some embodiments, theuser may request information through voice commands. In otherembodiments, the user may request information through tactile input(e.g., user interface 702), via a mobile device (e.g., user device 612),etc.

Process 3300 continues with step 3304, in which user control device hasobtained the requested information, and transmits the information to theuser. In some embodiments, control device 214 provides the informationto the user through speakers. In other embodiments, control device 214may transmit the information through text, images, etc. In thisexemplary embodiment, the information is presented through an interfaceof a companion application for control device 214. The exemplaryembodiment includes a room status indicator 3306. The exemplaryembodiment also includes a menu option 3308. The exemplary embodimentincludes a message 3310 that greets the user and provides relevantinformation. For example, if the user is leaving the hotel on that day,message 3310 may include the time of checkout.

The exemplary embodiment includes an information section 3312 thatprovides relevant information regarding attractions and accommodations.In some embodiments, the attractions and accommodations are local to thehotel. In other embodiments, a user may specify the location, distance,price, etc. Control device 214 may store the information. In someembodiments, control device 214 may access the information from anoutside site, such as Yelp, Google Reviews, etc.

The exemplary embodiment includes a navigation section 3314 thatprovides navigation tools. In some embodiments, the tools are buttonsrepresented by icons. In other embodiments, the tools may be text links,check boxes, etc. Navigation section 3314 may be customized to providerelevant options. The exemplary embodiment further includes a systemindicator 3316. The exemplary embodiment further includes a page title3318.

Process 3300 continues with step 3318, in which a screen showsaccommodations available at the hotel. A user may input a selectionthrough control device 214 by any means previously described.

Process 3300 continues with step 3320, in which a screen showing afloorplan is displayed on control device 214. In some embodiments, thefloorplan may display a user selection, such as a pool. In thisexemplary embodiment, the user selected the pool from the screen ofcontrol device 214. The location of the pool on the floorplan is shownon the screen. In other embodiments, other information may be shown oncontrol device 214, as described earlier.

Referring now to FIG. 34, a process 3400 is shown for assisting a userwith checkout without having to go to the front desk. Process 3400begins with step 3402, in which control device 214 presents a checkoutscreen to the user. In some embodiments, the screen is presentedautomatically at checkout time. In other embodiments, the screen may berequested by the user. The screen may include information such as theroom number, incidental charges, total charges, tip amounts, etc.Process 3400 may not proceed without confirmation from the user that theinformation presented is correct, and that she accepts all chargesshown.

Process 3400 continues with step 3404, in which control device 214thanks the user for staying with the hotel with a parting message. Insome embodiments, the parting message may be customized to the user'sliking. In other embodiments, the parting message is customized for thehotel. The parting message may be delivered in any way. In someembodiments, the parting message is delivered via speakers. In otherembodiments, the parting message is delivered as text, images, etc. Theparting message may be accompanied by a receipt for the total of thestay. In some embodiments, the receipt may be printed by control device214. In other embodiments, the receipt may be printed at the front deskand delivered to or picked up by the user. Process 3400 may be executedby control device 214 and/or hotel module 750.

In some embodiments, control device 214 prompts the user to enterpayment information and/or swipe a credit and/or debit card via inputdevice 712. This may allow the user to pay for their stay and/or anyadditional charges without stopping at the front desk. In someembodiments, the control device facilitates transfer of funds from afinancial account associated with a user to a financial accountassociated with the hotel. The financial account may be held withfinancial institution system 3504 and control device 214 may facilitatethe transfer of funds with hotel module 750 and payment module 758. Insome embodiments, the user is required to swipe their card with inputdevice 712 at the beginning of their stay and simply confirm the amountand/or leave a tip when their stay expires.

Payment Features

Referring to FIGS. 35-39, in some embodiments, control device 214 mayinclude payment features allowing a user to make payments with a varietyof different devices using a variety of different payment protocols. Forexample, control device 214 may be installed in any location in which auser may make a payment directly, without the involvement of a cashieror other worker, such as in a vehicle (e.g., a taxi), a parkingstructure, a public transportation station, a hotel, or a retaillocation (e.g., a store checkout line, a trade show, a convention,etc.).

Referring specifically to FIG. 35, payment module 758 is shown indetail. Payment module 758 is shown to interact with user interface 702,input device 712, financial institution system 3504, and network 602. Insome embodiments, payment module 758 may interact with a remote device3506. Remote device 3506 may be any device providing data related to afinancial transaction. For example, remote device 3506 may be a cashregister or terminal, a taximeter, a mobile device, or any other devicecapable of providing data related to a financial transaction. The remotedevice may be directly coupled to control device 214 and directlycommunicates with control device 214 with a wired or wirelessconnection. In some embodiments, remote device 3506 is coupled tocontrol device 486 through network 602 and communicates with controldevice 214 through the network 602.

Referring now to FIG. 36, a block diagram illustrating an input device712 of user control device 468 is shown, according to an exemplaryembodiment. Input device 712 is shown to include a card reading device3602. Card reading device 3602 may be any device that is able to receiveinformation from a card (e.g., credit card, debit card, gift card,commuter card, etc.).

Referring to FIG. 37, a diagram of a control device processing paymentwith an input device, according to an exemplary embodiment. In oneembodiment, card reading device 3602 may be a magnetic strip reader thatis configured to receive information encoded in a magnetic strip on thecard. Information encoded on a magnetic strip of the user's card may beread by the card reading device by inserting the card into the cardreading device or by swiping the card through the card reading device.In another embodiment, card reading device 3602 may be a chip readerthat is configured to receive information encoded on a microchip on thecard. Information encoded on the microchip of the user's card may beread by the card reading device by inserting the card into card readingdevice 3602. In another embodiment, card reading device 3602 may useanother technology to receive information encoded on the user's card.For example, card reading device 3602 may include an infrared scanningmechanism to read information encoded in a bar code on the user's card.

In some embodiments, input device 712 (e.g., card reader, wirelessreader, etc.) may be integrated into the user control device. Forexample, input device 712 may be integrally formed with the display orthe base. In other embodiments, input device 712 may be coupled to thedisplay or the base (e.g., as an aftermarket device, etc.). In otherembodiments, input device 712 may be separate from control device 214and may be connected to control device 214 through a wired connection ora wireless connection.

Referring now to FIG. 38, a diagram of control device 214 processing apayment with input device 712 is shown, according to an exemplaryembodiment. In FIG. 38, control device 214 is shown to include inputdevice 712 that is able to receive information from card 3802 (e.g.,credit card, debit card, gift card, commuter card, etc.) or user device612 without physically interacting with the card or mobile device usinga wireless protocol (e.g., ZigBee, Bluetooth, Wi-Fi, NFC, RFID, etc.).In one exemplary embodiment, a user may make a payment by passing adevice capable of NFC communication in close proximity to the usercontrol device to make a payment using a mobile payment service (e.g.,Apple Pay, Google Wallet, Android Pay, etc.).

Referring now to FIG. 39, a process 3900 for making a payment with usercontrol device 214 is shown according to some embodiments. In someembodiments, process 3900 is performed by payment module 758 of controldevice 214. Process 3900 begins with step 3902 in which transaction datais entered and the transaction data is communicated to control device214. In some embodiments, the transaction data may be entered directlyinto control device 214 with user interface 702. In some embodiments,the transaction data is received from a remote device. For example,transaction data may be received from a cash register, a paymentterminal, a taximeter, a mobile device, etc.

The process continues with step 3904 in which payment data is receivedby user control device 214. Payment data may be received, for example,by swiping a card through a card reader (e.g., input device 712, cardreading device 3602, etc.), inserting a card into a card reader, passinga card under a sensor (e.g., an infrared sensor), or holding a card ormobile device close to control device 214. The payment data may includevarious information such as authentication data, encryption data,decryption data, etc.

The process continues with step 3906 in which user control device 214communicates with financial institution system 3504 to authorize thepayment. Financial institution system 3504 may, for example, be a creditcard company or a banking network. The control device 214 communicates avariety of information to financial institution system 3504 includingpayment data and transaction data to authorize the payment.

Thermostat with Direction Display

Referring now to FIG. 40, a block diagram of communications system 4000is shown, according to an exemplary embodiment. System 4000 can beimplemented in a building (e.g. building 10) and is shown to includedisplay device 4002, network 4004, building emergency sensor(s) 4006,weather server(s) 4008, building management system 4010, social mediaserver(s) 4011, and user device 4012. System 4000 connects devices,systems, and servers via network 4004 so that emergency information,navigation directions, and other information can be passed betweendevices (e.g., display device 4002, user device 4012, building emergencysensor(s) 4006) and servers and systems (e.g., social media server(s)4011, weather server(s) 4008, and building management system 4010).

In some embodiments, network 4004 communicatively couples the devices,systems, and servers of system 4000. In some embodiments, network 4004is at least one of and/or a combination of a Wi-Fi network, a wiredEthernet network, a Zigbee network, a Bluetooth network, and/or anyother wireless network. Network 4004 may be a local area network or awide area network (e.g., the Internet, a building WAN, etc.) and may usea variety of communications protocols (e.g., BACnet, IP, LON, etc.).Network 4004 may include routers, modems, and/or network switches.Network 4004 may be a combination of wired and wireless networks.

In some embodiments, display device 4002 is configured to receiveemergency information and navigation directions via network 4004. Insome embodiments, display device 4002 is a wall mounted device with adisplay screen. For example, display device 4002 can be a thermostat, ahumidistat, a light controller, and any other wall mounted device with adisplay screen. In some embodiments, display device 4002 is connected tobuilding emergency sensor(s) 4006 and receives emergency data from thebuilding emergency sensor(s) 4006. In some embodiments, buildingemergency sensor(s) 4006 are sensors which detect building emergencies.Building emergency sensor(s) 4006 can include, for example, smokedetectors, carbon monoxide detectors, fire pull handles, panic buttons,gunshot detection sensors, and any other emergency sensor. In someembodiments, the emergency sensor(s) include actuators. The actuatorsmay be building emergency sirens, a sprinkler and/or sprinkler system,an automatic door controller and/or automatic door control system, andany other actuator used in a building. In some embodiments, buildingemergency sensor(s) 4006 may communicate with building management system4010. Building management system 4010 may sensor data from the buildingemergency sensor(s) 4006. In various embodiments, building managementsystem 4010 may send the sensor data and/or emergency informationassociated with the sensor data to display device 4002.

In some embodiments, display device 4002 is communicatively coupled toweather server(s) 4008 via network 4004. In some embodiments, displaydevice 4002 is configured to receive weather alerts (e.g., high and lowdaily temperature, five-day forecast, thirty-day forecast, etc.) fromthe weather server(s) 4008. Display device 4002 may be configured toreceive emergency weather alerts (e.g., flood warnings, fire warnings,thunder storm warnings, winter storm warnings, etc.) from the weatherserver(s) 4008. In some embodiments, display device 4002 is configuredto display emergency warnings via a user interface of display device4002 when display device 4002 receives an emergency weather alert fromweather server(s) 4008. Display device 4002 may be configured to displayemergency warnings based on the data received from building emergencysensor(s) 4006. In some embodiments, display device 4002 causes a sirento alert occupants of the building of an emergency, causes all doors tobecome locked and/or unlocked, causes an advisory message be broadcastthrough the building, and/or controls any other actuator or systemnecessary for responding to a building emergency. In some embodiments,the building management system 4010 communicates with weather server4008. Building management system 4010 may communicate (e.g., send)information from weather server 4008 to display device 4002.

In some embodiments, display device 4002 is configured to communicatewith building management system 4010 via network 4004. Display device4002 may be configured to transmit environmental setpoints (e.g.,temperature setpoint, humidity setpoint, etc.) to building managementsystem 4010. In some embodiments, building management system 4010 isconfigured to cause zones of a building (e.g., building 10) to becontrolled to the setpoint received from display device 4002. Forexample, building management system 4010 may be configured to controlthe temperature, humidity, lighting, or other environmental conditionsof a building based on the setpoints or control signals received fromdisplay device 4002. In some embodiments, building management system4010 is configured to transmit emergency information to display device4002. The emergency information can include, for example, a notificationof a shooter lockdown, a tornado warning, a flood warning, athunderstorm warning, and/or any other warning. In some embodiments,building management system 4010 is connected to various weather serversand/or other web servers from which building management system 4010receives emergency warning information.

In some embodiments, the display device 4002 is configured tocommunicate with one or more social media server(s) 4011 via network4004. Social media server(s) 4011 may include, but are not limited to,servers supporting Facebook, Instagram, Twitter, Snapchat, WhatsApp,and/or other social media platforms. In some embodiments, the displaydevice 4002 may have a profile or other presence on a social mediaplatform, such that a user may send a direct message, post, tweet, etc.to the display device 4002. For example, a user may tweet at (i.e., viaTwitter) or send a direct message to (e.g., via Facebook Messenger,WhatsApp, etc.) the display device 4002 and/or the building managementsystem 4010 to indicate that an emergency is ongoing in a building(e.g., “@displaydevice4002 a fire just started in Room X”). The displaydevice 4002 may receive such a message, tweet, post, etc., extractrelevant information therefrom using a natural language processingapproach, and generate emergency directions based on the extractedinformation. In some embodiments, the display device 4002 is configuredto send a message or comment to the user in response, for example usingan automated chat bot approach.

In various embodiments, the display device 4002 accesses the socialmedia server(s) to passively monitor social media activity of one ormore occupants of a building to identify events in a building and/oremergencies in a building. For example, the display device 4002 mayaccess a message sent from a first user of a social media server 4011 toa second user of the social media server 4011 which mentions an ongoingemergency in the building. As another example, the display device 4002may analyze pictures and/or videos posted publically by a social mediauser (e.g., via Snapchat, Instagram, etc.) to identify buildingoccupancy, events in the building, emergencies in the building, etc. andrespond accordingly. For example, a user may post a video that shows anactive shooter in a building, and the display device 4002 may receivesaid video, analyze said video to determine a location of the shooter inthe building, and generate one or more directions to provide to one ormore building occupants to help the occupants find safety. Various suchinteractions between the social media server(s) 4011 and the displaydevice 4002 are contemplated by the present disclosure.

Display device 4002 can be configured to communicate with user device4012 via network 4004. In some embodiments, user device 4012communicates calendar information to display device 4002. User device4012 can include any user-operable computing device such as smartphones,tablets, laptop computers, desktop computers, wearable devices (e.g.,smart watches, smart wrist bands, smart glasses, etc.), and/or any othercomputing device. User device 4012 can be a mobile device or anon-mobile device. In some embodiments, the calendar information isstored and/or entered by a user into calendar application 4014. Calendarapplication 4014 may be one or a combination of Outlook, GoogleCalendar, Fantastical, Shifts, CloudCal, DigiCal, and/or any othercalendar application. Display device 4002 may receive calendarinformation from the calendar application such as times and locations ofappointments, times and locations of meetings, information about theexpected location of the user, and/or any other calendar information.Information about the expected location of the user may be informationthat the user will depart for an airport or another location at aspecific time or in a range of times. Display device 4002 may beconfigured to display direction to a user associated with user device4012 based on the calendar information stored in calendar application4014.

In various embodiments, the user device 4012 provides various data andinformation regarding use of the user device 4012 to the display device4002 and/or the building management system 4010. For example, thedisplay device 4002 may collect a live feed of the usage of the userdevice 4012 to facilitate identification and characterization ofbuilding emergencies and/or to facilitate the provision of directions toa user in case of an emergency. For example, the display device 4002 mayreceive data relating to an emergency call made by the user device 4012,the location of the user device 4012 (e.g., based on GPS data collectedby the user device 4012), social media activity of a user of the userdevice 4012, etc. In some embodiments, the display device 4002 activatesa microphone and/or camera of the user device 4012 in an emergencysituation to monitor the safety of a user in an emergency situation.

In some embodiments, a user may press a button on a user interface ofdisplay device 4002 indicating a building emergency. The user may beable to indicate the type of emergency (e.g., fire, flood, medical,active shooter, etc.). Display device 4002 may communicate an alert tobuilding management system 4010, user device 4012, social media server4011 and/or any other device, system, or server. For example, displaydevice 4002 may be configured to cause the social media server 4011 togenerate a social media notification relating to a building emergencyfor a user.

Referring now to FIG. 41, a block diagram of communications system 4100is shown, according to an exemplary embodiment. System 4100 can beimplemented in a building (e.g. building 10) and is shown to includedisplay device 4002, network 4004, building emergency sensor(s) 4006,weather server(s) 4008, building management system 4010, and user device4012. These components may be the similar or the same as described withreference to FIG. 40. System 4100 connects devices, systems, and serversvia network 4004 so that emergency information, navigation directions,and other information can be passed between devices (e.g., displaydevice 4002, user device 4012, building emergency sensor(s) 4006) andservers and systems (e.g., weather server(s) 4008 and buildingmanagement system 4010).

In some embodiments, system 4100 includes display devices 4016 and 4018.Display devices 4016 and 4018 may be identical and/or similar to displaydevice 4002. In some embodiments display devices 4016 and 4018 have theability to communicate to display device 4002 but are different fromdisplay device 4002. For example, display device 4016 and display device4018 can be smart actuators, building controllers, etc., while displaydevice 4002 can be a smart thermostat. Display device 4002, displaydevice 4016, and display device 4018 may be located in differentlocations of a building (e.g., building 10). In some embodiments,display device 4002, display device 4016, display device 4018 and userdevice 4012 may communicate to each other ad hoc. In some embodiments,display device 4002, display device 4016, and display device 4018 maycommunicate to each other via network 4004. In some embodiments, ad hoccommunication may be at least one of (ad hoc Wi-Fi, ad hoc Zigbee, adhoc Bluetooth, NFC, etc.) In some embodiments, the devices form a MANET,a VANET, a SPAN, an IMANET, and/or any other ad hoc network. In someembodiments, the devices are connected and communicate via RS-485,Ethernet, and/or any other wired, wireless, or combination of wired andwireless communication method.

In some embodiments, display device 4002, display device 4016, displaydevice 4018 send navigation directions to one another via ad hoccommunication. In some embodiments, one of the display devicesdetermines a route for a building occupant. The route may be the fastestor shortest path to a destination (e.g., a conference room, an office,etc.). Display device may handoff the navigation directions to otherdisplay devices (e.g., display device 4016, display device 4018, etc.)along the path of the occupant. In some embodiments, the route may meeta need of the occupant, such as a route that will accommodatewheelchairs if the occupant is in a wheelchair or traveling with someonein a wheelchair.

In some embodiments, user device 4012 is configured to communicate withdisplay device 4002, display device 4016, and display device 4018 via adhoc communication. In some embodiments, user device 4012 may communicatewith the display devices (e.g., display device 4002, display device4016, display device 4018, etc.) and request navigation directions. Insome embodiments, a user may check in with a display device and thedisplay device may display navigation information for the individualassociated with the user device 4012. Checking in with the displaydevice may be holding user device 4012 a certain distance from thedisplay device so that user device 4012 can communicate with the displaydevice via NFC. In various embodiments, checking in with the displaydevice includes connecting to the display device via Wi-Fi, Bluetooth,or Zigbee and entering a password and/or username.

Referring now to FIG. 42, a block diagram illustrating display device4002 in greater detail is shown, according to an exemplary embodiment.Display device 4002 is shown to include a communications interface 4202,an occupancy sensor 4204, a speaker 4206, a user interface 4208, and aprocessing circuit 4210. Display device 4002 can be configured todisplay directions and/or other types of information to a user via userinterface 4208. In some embodiments, display device 4002 is configuredto determine a highest priority direction and/or emergency notificationand display the direction and/or emergency notification on userinterface 4208. In some embodiments, displaying the directions on userinterface 4208 is accompanied by playing the direction and/or emergencynotification via speaker 4206. The priority of direction and/oremergency notification may be determined based on detecting emergencies,identifying users with occupancy sensor 4204, and receiving directionsover communications interface 4202.

Communications interface 4202 may be configured to communicate withnetwork 4004 as described with reference to FIGS. 40-41. Communicationsinterface 4202 can be configured to communicate via local area networks(e.g., a building LAN), wide area networks (e.g., the Internet, acellular network, etc.), conduct direct communications (e.g., NFC,Bluetooth, etc.) ad hoc with devices (e.g., ad hoc Wi-Fi, ad hoc Zigbee,ad hoc Bluetooth, NFC etc.), and/or with ad hoc networks (e.g., MANET, aVANET, a SPAN, an IMANET, and any other ad hoc network). In someembodiments, communications interface 4202 communicates ad hoc withdisplay device 4002, display device 4016, and/or display device 4018. Insome embodiments, communications interface 4202 includes an applicationgateway configured to receive input from applications running on clientdevices. Communications interface 4202 can include one or more wirelesstransceivers (e.g., a Wi-Fi transceiver, a Bluetooth transceiver, a NFCtransceiver, a cellular transceiver, etc.) for communicating with mobiledevices.

In some embodiments, communications interface 4202 communicates withdisplay device 4016, display device 4018, building emergency sensor(s)4006, weather server(s) 4008, building management system 4010, and/oruser device 4012 as described with reference to FIGS. 40-41 to receiveenvironmental condition information, direction requests and/or emergencynotifications. Communications interface 4202 may receive navigationrequests from user device 4012. Communications interface 4202 mayreceive navigation direction and/or building maps from buildingmanagement system 4010. In some embodiments, emergency informationand/or alerts are received via communications interface 4202 frombuilding management system 4010. In some embodiments, emergencyinformation is received form building emergency sensor(s) 4006. In someembodiments, emergency information is received from weather server(s)4008.

Occupancy sensor 4204 may be used to detect occupancy and determine theidentity of the occupant. Occupancy sensor 4204 may be one or acombination of motion sensors, cameras, microphones, capacitive sensors,or any number of other sensors. For example, occupancy sensor 4204 caninclude one or more cameras which detect heat signatures. Occupancysensor 4204 may detect separate objects and distinguish between humansand other objects. Occupancy sensor 4204 can include one or moretransducers which detect some characteristic of their respectiveenvironment and surroundings. Occupancy sensors, such as a camera, maybe used to determine if an occupant is using a wheelchair, cane,crutches, and/or any other assistance device.

Speaker 4206 may be configured to project audio. The audio may bewarning messages, direction messages, alternate route suggestionmessages and any other message. Speaker 4206 may be any kind ofelectroacoustic transducer and/or combination of transducers that areconfigured to generate sound waves based on electrical signals. Speaker4206 may be a loudspeaker (e.g., various combinations of subwoofers,woofers, mid-range drivers, tweeters, etc.) and may broadcast messagesto an entire zone and/or an entire building (e.g., building 10). In someembodiments, speaker 4206 includes filters. In some embodiments, thefilters are various combinations of high pass filters, low pass filters,band pass filters, etc.

User interface 4208 may be a touch screen display configured to receiveinput from a user and display images and text to a user. In someembodiments, user interface 4208 is at least one or a combination of aresistive touch screen and a capacitive touch screen (e.g., projectivecapacitive touch screen). In some embodiments, user interface 4208 is aswept-volume display, a varifocal mirror display, an emissive volumedisplay, a laser display, a holographic display, a light field display,and/or any other display or combination of displays. User interface 4208may be configured to display images and text to a user but may not beconfigured to receive input from the user. In some embodiments, userinterface 4208 is one or a combination of a CRT display, an LCD display,an LED display, a plasma display, and/or an OLED display.

Processing circuit 4210 is shown to include a processor 4212 and memory4214. Processor 4212 can be a general purpose or specific purposeprocessor, an application specific integrated circuit (ASIC), one ormore field programmable gate arrays (FPGAs), a group of processingcomponents, or other suitable processing components. Processor 4212 maybe configured to execute computer code and/or instructions stored inmemory 4214 or received from other computer readable media (e.g., CDROM,network storage, a remote server, etc.).

Memory 4214 can include one or more devices (e.g., memory units, memorydevices, storage devices, etc.) for storing data and/or computer codefor completing and/or facilitating the various processes described inthe present disclosure. Memory 4214 can include random access memory(RAM), read-only memory (ROM), hard drive storage, temporary storage,non-volatile memory, flash memory, optical memory, or any other suitablememory for storing software objects and/or computer instructions. Memory4214 can include database components, object code components, scriptcomponents, or any other type of information structure for supportingthe various activities and information structures described in thepresent disclosure. Memory 4214 can be communicably connected toprocessor 4212 via processing circuit 4210 and can include computer codefor executing (e.g., by processor 4212) one or more processes describedherein.

Memory 4214 is shown to include a network controller 4216, an emergencyidentifier 4218, a HVAC controller 4226, a directions controller 4228, adirection selector 4244, an occupancy controller 4238, an audiocontroller 4240, and user interface controller 4242. Each of thesecomponents is described in greater detail below.

Network controller 4216 may contain instructions to communicate with anetwork (e.g., network 4004) and ad hoc to other devices (e.g., displaydevice 4016, display device 4018, user device 4012, etc.). In someembodiments, network controller 4216 contains instructions tocommunicate over wireless and wired communication methods. In someembodiments, wireless communication methods are communicating in a Wi-Finetwork, a Zigbee network, and/or a Bluetooth network via communicationsinterface 4202. In some embodiments, the communication methods are wiredsuch as via RS-485, Ethernet (e.g., CATS, CAT5e, etc.), and/or any otherwired communication method. Network controller 4216 may be configured tofacilitate communication a local area network or a wide area network(e.g., the Internet, a building WAN, etc.) and may be configured to usea variety of communications protocols (e.g., BACnet, IP, LON, etc.). Insome embodiments, network controller 4216 facilitates ad hoccommunication. The ad hoc communication may be at least one of (ad hocWi-Fi, ad hoc Zigbee, ad hoc Bluetooth, NFC etc.). In some embodiments,network controller 4216 facilitates communication over an ad hoc network(e.g., MANET, a VANET, a SPAN, an IMANET, and any other ad hoc network).

Emergency identifier 4218 can be configured to determine whether anemergency is occurring. The emergency can be an emergency inside thebuilding (e.g., a fire, a dangerous person, a critical fault oroperating condition in the BMS, etc.) or an emergency outside thebuilding (e.g., a tornado, dangerous weather conditions, etc.). In someembodiments, emergency identifier 4218 is configured to determineemergency alerts based on information received from network controller4216. Emergency identifier 4218 may include emergency sensor controller4220, weather server controller 4222, and BMS emergency controller 4224.Emergency sensor controller 4220 may be configured to communicate withbuilding emergency sensor(s) 4006 described with reference to FIGS.40-41 via network controller 4216 and communications interface 4202. Insome embodiments, emergency sensor controller 4220 can send commands tobuilding emergency sensor(s) 4006. In some embodiments, the commands areto activate actuators, deactivate actuators, gather sensor data, etc.and are sent to emergency sensor(s) 4006 and/or emergency sensorcontroller 4220.

Emergency sensor controller 4220 may receive sensor data from buildingemergency sensor(s) 4006 via network controller 4216 and communicationsinterface 4202. Emergency sensor controller 4220 may be configured toanalyze the sensor data and determine if an emergency is present.Emergency sensor controller 4220 may determine the nature and/orlocation of the emergency based on the analysis of the sensor data. Thenature of the emergency may be an earthquake, a fire, a gas leak, etc.Emergency sensor controller 4220 may be configured to determine and/orretrieve applicable directions for the determined emergency. In someembodiments, emergency sensor controller 4220 determines that anemergency is occurring when the sensor data is above and/or below apredefined threshold. For example, if emergency sensor controller 4220determines that sensor data/information indicates that carbon monoxidelevels cross a predefined threshold, the air is dangerous to breath andthe building should be evacuated.

In some embodiments, building emergency sensor(s) 4006 are configured todetermine the nature of the emergency. Emergency sensor controller 4220may be configured to receive the nature of the emergency from buildingemergency sensor(s) 4006 via network controller 4216 and communicationsinterface 4202. Emergency sensor controller 4220 can be configured togenerate emergency directions based on the emergency. In someembodiments, the emergency directions are to evacuate a building, hideunder tables and/or desks, close windows, and any other directionrelevant to an emergency situation. Emergency sensor controller 4220 maysend the determined emergency directions to direction selector 4244.

In some embodiments, the building emergency sensor(s) 4006 areconfigured to identify a location of an emergency in the building (e.g.,a location of a fire, a location of an active shooter) and the emergencysensor controller 4220 is configured to receive the location of theemergency from the building emergency sensor(s) 4006 via networkcontroller 4216 and communications interface 4202. In such embodiments,the emergency sensor controller 4220 can be configured to generateemergency directions based on the location of the emergency, for exampleto direct a user away from the emergency (e.g., away from a fire, awayfrom an active shooter, along an evacuation route that avoids adangerous area). The emergency directions may update dynamically as theemergency moves through a building, e.g., as the emergency sensor(s)4006 detect the emergency (e.g., a fire, a gunshot) in changinglocations in the building.

In some embodiments, the existence, nature, and/or location of anemergency may be determined based at least in part on live data receivedfrom the user device 4012 and/or other web-based live data streams(e.g., social media). For example, the emergency identifier 4218 mayreceive an indication of a call or message transmitted from the userdevice 4012 to an emergency response system. As another example, theemergency identifier 4218 may receive social media posts that indicatethat an emergency event is occurring. The emergency identifier 4218 mayuse this live data to identify an ongoing emergency and/or determine thenature and/or location of the emergency.

Weather server controller 4222 may be configured to communicate withweather server(s) 4008 as described with reference to FIGS. 4-5. Weatherserver controller 4222 may be configured to query weather server(s) 4008for weather information and/or weather related emergency information. Insome embodiments, weather server controller 4222 is configured todetermine emergency directions based on the information received fromweather server(s) 4008. The emergency directions may be sent todirection selector 4244. In some embodiments, the directions are toevacuate a building, hide under tables and/or desks, close windows, andany other direction relevant to an emergency situation.

BMS emergency controller 4224 may be configured to communicate withbuilding management system 4010 as described with reference to FIGS.4-5. In some embodiments, BMS emergency controller 4224 may beconfigured to receive emergency information from building managementsystem 4010. In some embodiments, the information received is weatherrelated emergencies, active shooter emergencies, unsafe buildingemergencies, and any other emergency information received from buildingmanagement system 4010. In some embodiments, BMS emergency controller4224 is configured to send the emergency information received formbuilding management system 4010 to direction selector 4244.

In some embodiments, building management system 4010 may include one ormore databases which store building maps, room and meeting schedules,and/or any other information regarding a building (e.g., building 10).In some embodiments, BMS emergency controller 4224 is configured torequest the building information from building management system 4010and send the building related information to directions controller 4228.

Still referring to FIG. 42, HVAC controller 4226 may communicate withthe building management system 4010 via network controller 4216,communications interface 4202, and network 4004 as described withfurther reference to FIGS. 4-5. HVAC controller 4226 may be configuredto receive temperature setpoints and humidity setpoints via userinterface 4208. In some embodiments, HVAC controller 4226 provides acontrol signal to building management system 4010 via network controller4216 and/or communications interface 4202. The control signal may causethe building management system 4010 to condition and/or heat a zoneand/or building to a setpoint temperature. Further, the control signalsmay cause building management system 4010 to achieve a humidity value ina building and/or zone based on a humidity setpoint.

HVAC controller 4226 may use any of a variety of control algorithms(e.g., state-based algorithms, extremum-seeking control algorithms, PIDcontrol algorithms, model predictive control algorithms, feedbackcontrol algorithms, etc.) to determine appropriate control actions forany HVAC equipment connected to building management system 4010 as afunction of temperature and/or humidity. For example, if the temperatureis above a temperature set point received from user interface 4208, HVACcontroller 4226 may determine that a cooling coil and/or a fan should beactivated to decrease the temperature of a supply air delivered to abuilding zone. Similarly, if the temperature is below the temperatureset point, HVAC controller 4226 may determine that a heating coil and/ora fan should be activated to increase the temperature of the supply airdelivered to the building zone. HVAC controller 4226 may determine thata humidification or dehumidification component of building managementsystem 4010 should be activated or deactivated to control the ambientrelative humidity to a humidity set point for a building zone.

Directions controller 4228 may be configured to determine directions foran occupant or a group of occupants of a building (e.g., building 10).In some embodiments, directions controller 4228 includes anopportunistic controller 4230, a user based direction controller 4232, aspecial needs controller 4234, and a direction request controller 4236.Opportunistic controller 4230 may be configured to generate and/ordetermine building event directions and/or messages based on informationreceived from the building management system 4010. In some embodiments,opportunistic controller 4230 is configured to receive building eventinformation from building management system 4010 and/or calendarapplication 4014 of user device 4012 as described with reference toFIGS. 4-5. In some embodiments, the event information may include animage to display on user interface 4208. The event information mayinclude all events in a building at a specific time. Opportunisticcontroller 4230 may be configured to determine if the location of theevent is nearby the location of display device 4002. In someembodiments, only events that are nearby the location of the displaydevice 4002 are determined to be displayed on user interface 4208.

In some embodiments, opportunistic controller 4230 analyzes calendarinformation from one or more mobile devices (e.g., user device 4012)received via network controller 4216 and communications interface 4202.Based on the calendar information, display device 4002 may learn whatevents are occurring in the building. Opportunistic controller 4230 maybe configured to generate an event image (e.g., various combinations oflogos, admission fees, locations, start and end times, etc.) relating tothe event and may determine proper audio notifications to be servedalong with the generated event image.

User-based direction controller 4232 may be configured to generatenavigation directions for an occupant. In some embodiments, user baseddirection controller 4232 may be configured to receive the identity ofan occupant from occupancy controller 4238. The identity may be theidentity of an occupant a predetermined distance from display device4002. In some embodiments, the user based direction controller 4232 maybe configured to query the building management system 4010 via networkcontroller 4216 and communications interface 4202 for informationassociated with the identified occupant. In some embodiments, buildingmanagement system 4010 may reply with the name of the occupant, theschedule of the occupant, any meetings and/or events that the occupantis a participant (e.g., optional participant, required participant,etc.), and may also reply with any special needs of the occupant, suchas wheel chair accessible directions. User based direction controller4232 may be configured to generate directions to any locations which theidentified occupant may be scheduled to be. In some embodiments, userbased direction controller 4232 may be configured to communicate with acalendar application (e.g., calendar application 4014) via ad hoc and/ornetwork communications with a user device (e.g., user device 4012) todetermine the schedule of a building occupant. In some embodiments, userbased direction controller 4232 may be configured to generate arrows,building maps, audio directions, and any other form of directions. Userbased direction controller 4232 may be configured to send the directionsto direction selector 4244.

Special needs controller 4234 may determine if the occupant identifiedby user based direction controller 4232 has any special needs. Forexample, special needs controller 4234 may be configured to communicatewith building management system 4010 and receive any informationrelating to any physical and/or mental disabilities associated with theidentified user. The disabilities may be that the identified occupant isdeaf, mute, blind, in a wheelchair, on crutches, etc. In someembodiments, special needs controller 4234 may determine buildingdirections based on the disability of the occupant. For example, if theidentified occupant is in a wheel chair, the special needs controller4234 may generate directions to a location that circumnavigates anystairs. If the identified occupant is determined to be deaf, the specialneeds controller 4234 may be configured to generate audio directionsonly and not visual directions. In some embodiments, the audiodirections are a series of turns (e.g., “go forward to end of hall turnright, go forward to end of hall turn left,” etc.)

Direction request controller 4236 may be configured to receive directionrequests from user interface 4208. Direction request controller maycommunicate with user interface controller 4242 and may receive thedirection request form user interface controller 4242. In someembodiments, direction request controller 4236 is configured to displaydirections to a requested location in response to a building occupantrequesting directions via user interface 4208. The requested locationcan include, for example, a conference room, a meeting room, an office,etc. In some embodiments, direction request controller 4236 may beconfigured to display a map showing where the user is, where thedestination is, the shortest route to the destination, etc. In someembodiments, direction request controller 4236 is configured to generatetext directions indicating which turns to make in order to navigate tothe destination. Further, direction request controller 4236 may beconfigured to generate audio messages to be played along with the visualdirections.

In some embodiments, occupancy controller 4238 may be configured todetermine the identity of an occupant based on information received fromoccupancy sensor 4204. The identity of the occupant may be provided touser based direction controller 4232. In some embodiments, the occupancycontroller 4238 receives sensor input from occupancy sensor 4204 wherethe sensor may be a camera. Occupancy controller 4238 can performdigital image processing to identify the one or more users based on thedigital images received from the camera. In some embodiments, digitalimage processing is used to identify the faces of the one or more users,the height of the one or more users, or any other physicalcharacteristic of the one or more users. In some embodiments, thedigital image processing is performed by image analysis tools such asedge detectors and neural networks. In some embodiments, the digitalimage processing compares the physical characteristics of the one ormore users with physical characteristics of previously identified users.

In some embodiments, occupancy controller 4238 receives sensor inputfrom a microphone. The microphone can be any of a plurality ofmicrophone types. The microphone types include, for example, a dynamicmicrophone, a ribbon microphone, a carbon microphone, a piezoelectricmicrophone, a fiber optic microphone, a laser microphone, a liquidmicrophone, and an audio speaker used as a microphone. In someembodiments, the occupancy controller analyzes the audio data receivedfrom the microphone. In some embodiments, occupancy controller 4238identifies one or more users based on voice biometrics of the audioreceived from the microphone. Voice biometrics are the uniquecharacteristics of a speaker's voice. Voice biometrics include voicepitch or speaking style that result from the anatomy of the speaker'sthroat and/or mouth. In some embodiments, the voice biometrics of linkedusers is stored on display device 4002 in occupancy controller 4238. Insome embodiments, the voice biometrics are stored on building managementsystem 4010 and must be retrieved by occupancy controller 4238. In someembodiments, occupancy controller 4238 uses a text dependent voicerecognition technique. In some embodiments, occupancy controller 4238uses a text independent voice recognition technique to identify the oneor more users.

In some embodiments, occupancy controller 4238 uses the text dependentvoice recognition technique to identify the one or more users based on apassword or particular phrase spoken by one of the users. For example,the user may speak a phrase such as “This is Felix, I am home.”Occupancy controller 4238 can perform speech recognition to determinethe spoken phrase “This is Felix, I am home” from the audio datareceived form the microphone. In some embodiments, occupancy controller4238 uses one or a combination of a hidden Markov models, dynamic timewarping, neural networks to determine the spoken phrase, etc. Occupancycontroller 4238 compares the determined spoken phrase to phrases linkedto users. If the phrase, “This is Felix, I am home” matches a phraselinked to a user Felix, occupancy controller 4238 can identify the useras Felix. In some embodiments, the linked phrases are stored onoccupancy controller 4238. In various embodiments, the linked phrasesare stored on building management system 4010.

In some embodiments, occupancy controller 4238 is configured to captureaudio data from one or more users and perform pre-processing. In someembodiments pre-processing may be compressing the audio data, convertingthe audio data into an appropriate format, and any other pre-processingaction necessary. Occupancy controller 4238 may be configured totransmit the captured spoken audio data to a voice recognition servervia communications interface 4202 and network 4004 as described withreference to FIGS. 40-41. The voice recognition server may be configuredto determine the identity of the occupant and transmit the identity ofthe occupant to occupancy controller 4238.

Audio controller 4240 may be configured to receive audio directions fromdirection selector 4244. Audio controller 4240 may generate an analogsignal for speaker 4206 based on a digital audio signal from directionselector 4244. In some embodiments, audio controller 4240 may beconfigured to convert a digital audio signal into an analog audio signal(i.e., digital to audio conversion (DAC)). In some embodiments, audiocontroller 4240 may contain a text to speech application programinterface (API) that is configured to generate spoken words based on thereceived navigation direction. In some embodiments, the text to speechAPI is one or a combination of Watson Text to Speech, Cortana text tospeech, an open source text to speech API, a proprietary text to speechAPI, and/or any other text to speech API.

User interface controller 4242 may be configured to display images onuser interface 4208. The images can include, for example, maps, text,arrows, and/or any other image used to display direction to an occupantof a building. In some embodiments, user interface controller 4242 isconfigured to receive input from use interface 4208. The input may berotating a map, zooming in on a map, typing in a conference roomnavigation request, and any other input that can be received from userinterface 4208. In some embodiments, user interface controller 4242receives images to display from direction selector 4244. In someembodiments, user interface controller 4242 sends direction requests todirection request controller 4236.

Direction selector 4244 may be configured to receive directions fromdirection controller 4228. Direction selector 4244 may be configured toreceive emergency directions from emergency identifier 4218. In someembodiments, direction prioritization selector 4246 is configured toreceive the directions for directions controller 4228. Directionselector 4244 may be configured to prioritize the directions receivedfrom directions controller 4228 and the emergency directions receivedfrom emergency identifier 4218. Direction prioritization selector 4246may be configured to rank each direction request in order of highestpriority. In some embodiments, directions requested via user interface4208 may have the highest priority over opportunistic directions and/ordirection determined based on information from occupancy sensor 4204.The ranking system may contain a queue which directions may be placed.The length of time which a direction is in the queue may factor intodetermining the priority for that direction. For example, a conferenceadvertisement may be received from opportunistic controller 4230 and maybe placed into a display queue. The longer the advertisement sits in thequeue, the higher the priority level for the advertisement may grow.When the priority level crosses a predefined level, the advertisementmay be displayed and the priority level reset. In some embodiments, thepriority of a direction may determine the period of time that thedirection is displayed on user interface 4208.

In some embodiments, direction prioritization selector 4246 may providethe highest priority direction to emergency prioritization selector4248. Emergency prioritization selector may provide the directionsreceived from direction prioritization selector 4246 to user interfacecontroller 4242 if no emergency is present. If an emergency is present,emergency prioritization selector may provide the emergency directionsto user interface controller 4242 instead of the directions fromdirection prioritization selector 4246. In some embodiments, emergencydirections for multiple emergencies (e.g., floods, tornados, storms,earthquakes, etc.) may be ranked base on order of priority. For example,if emergency prioritization selector 4248 receives a notification fromemergency identifier 4218 that there is an active shooter in thebuilding (e.g., building 10) and a notification that there is aflooding, emergency prioritization selector 4248 may rank the activeshooter directions as higher priority, and may show these directionsexclusively and/or for longer periods of time. In some embodiments, thehighest priority emergency direction is the direction that is mostlikely to cause harm to occupants of the building.

In various embodiments, emergency prioritization selector 4248 maycombine emergency directions when occupants of the building must respondto multiple emergencies simultaneously. For example, if there is a fireand a tornado, the emergency prioritization selector 4248 may combinefire response directions with tornado response directions. Emergencyprioritization selector 4248 may create emergency messages which telloccupants of the building to go to a certain exit. The route to the exitmay bypass rooms and/or hallways with large windows. Emergencyprioritization selector 4248 may be able to combine any amount or typeof emergency directions.

Referring now to FIG. 43, display device 4300 is shown as an alternateembodiment of display device 4002. Some components of display device4300 are the same as display device 4002 as described with reference toFIGS. 40-42. These components include, communications interface 4202,occupancy sensor 4204, speaker 4206, user interface 4208, processingcircuit 4210, processor 4212, memory 4214, network controller 4216,emergency identifier 4218, emergency sensor controller 4220, weatherserver controller 4222, BMS emergency controller 4224, HVAC controller4226, occupancy controller 4238, audio controller 4240, user interfacecontroller 4242, direction selector 4244, direction prioritizationselector 4246, and emergency prioritization selector 4248. Displaydevice 4300 is shown to further include direction handoff controller4302. In some embodiments, display device 4300 has some or all of thefunctionality of display device 4002. Direction handoff controller 4302is shown to include building map controller 4304, user based handoffcontroller 4306, direction request handoff controller 4310, and displaydevice location controller 4308. Display device 4300 may be configuredto determine navigation direction and emergency directions as describedwith reference to display device 4002.

In addition to determining navigation directions, emergency directions,and prioritizing directions, display device 4300 may be configured tocommunicate with other display devices (e.g., display device 4016,display device 4018, etc.) and pass directions to other display devices.In some embodiments, display device 4300 passes direction to otherdisplay devices that are on the route of a navigation path. In someembodiments, the direction handoff is performed via network 4004 asdescribed with reference to FIGS. 4-5. In various embodiments, thedirection handoff is performed ad hoc (e.g., by sending the directionsdirectly from display device to display device).

Building map controller 4304 may be configured to maintain and/or storea building map. The building map may include multiple floors, multiplecampuses, etc. Building map controller 4304 may receive updates frombuilding management system 4010 via network 4004. In some embodiments,building map controller 4304 may be configured to receive a map whenfirst installed in the building. In some embodiments, building mapcontroller 4304 contains the locations of all other display devices inthe building. In some embodiments, building map controller 4304 isconfigured to receive map updates from building management system 4010.In various embodiments, building map controller 4304 may receive noticesfrom building management system 4010 that a hallway and/or exit may beclosed and/or blocked. In some embodiments, a hallway and/or exit may beblocked based on an emergency (e.g., a certain hallway is on fire and isnot transmissible by an occupant. In various embodiments, a hallwayand/or exit may be blocked when there are building renovations and/orrepairs being done in the building.

User based handoff controller 4306 may have all of the functionality ofuser based direction controller 4232 and special needs controller 4234.In addition to this functionality, user based handoff controller 4306may be configured to generate a message to send to other devices alongthe determined path and/or route. The other devices may be targetedbased on their location along the route. Further, the time at which theuser based handoff controller 4306 causes the message to be sent may bebased on an anticipated and/or determined walking speed of a user. Forexample, the message to display the directions for a user may bedisplayed when it is anticipated that the user will be passing the nextdisplay device based on an anticipated and/or determined walking speed.User based handoff controller 4306 may cause network controller 4216 andcommunications interface 4202 to send the message to other targeteddisplay devices.

Display device location controller 4308 may be configured to maintainthe location of the display device 4300. In some embodiments, displaydevice location controller 4308 may perform an initial configurationroutine in which the display device may prompt an installer with abuilding map and request that the installer identify the location of thedisplay device 4300. In some embodiments, a password may be entered viauser interface 4208 allowing an authorized individual to change thelocation of the display device 4300. In various embodiments, displaydevice location controller 4308 may be configured to periodically promptusers to confirm the location of the display device 4300. In variousembodiments, display device location controller 4308 may prompt the userby asking the user if the directions it is displaying are correct orincorrect. If the user indicates via user interface 4208 that thedirection displayed by display device location controller 4308 areincorrect, display device location controller 4308 may be configured tocause a message to be sent to building management system 4010. Buildingmanagement system 4010 may notify a building technician that thelocation of display device 4300 needs to be correct and/or updated.

Direction request handoff controller 4310 may contain some or all of thefunctionality of direction request controller 4236. In addition to thisfunctionality, direction request handoff controller 4310 may beconfigured to generate a message to send to other devices along thedetermined path and/or route. The other devices may be targeted based ontheir location along the route. Further, the time at which directionrequest handoff controller 4310 causes the message to be sent may bebased on an anticipated and/or determined walking speed of a user. Forexample, the message to display the directions for a user may bedisplayed when it is anticipated that the user will be passing the nextdisplay device based on an anticipated and/or determined walking speed.Direction request handoff controller 4310 may cause network controller4216 and communications interface 4202 to send the message to othertargeted display devices.

Referring now to FIG. 44, display device 4400 is shown as an alternateembodiment of display device 4002. In some embodiments display device4400 has some and/or all of the functionality of display device 4002.Various components of display device 4400 shown are the same as indisplay device 4002 as described with reference to FIGS. 4-6. Thecomponents include communications interface 4202, speaker 4206, userinterface 4208, processing circuit 4210, processor 4212, memory 4214,network controller 4216, HVAC controller 4226, emergency identifier4218, emergency sensor controller 4220, weather server controller 4222,BMS emergency controller 4224, audio controller 4240, and user interfacecontroller 4242. Display device 4400 may be configured to be removedfrom a wall (e.g., a wall mount) in the event of an emergency. In someembodiments, display device 4400 is configured to be torn off the wall.In various embodiments, display device 4400 unhooks from a wall mount sothat it can be easily removed. Display device 4400 may providenavigation directions for evacuating a building in case of a fire, anactive shooter, etc. Display device 4400 is shown to include batterycontroller circuit 4402, battery 4404, and GPS 4406. Memory 4214 isshown to include mobile display device controller 4408.

Battery controller circuit 4402 is configured to charge and/or dischargebattery 4404. Battery controller circuit 4402 may receive AC powerand/or DC power. Battery controller circuit 4402 may include a rectifiercircuit configured to convert the AC power into DC power. In someembodiments, the rectifier is a full wave rectifier, a half waverectifier, a full bridge rectifier, and any other type of rectifier. Insome embodiments, the rectified wave is filtered to smooth out anyvoltage ripple present after the wave is rectified. Battery controllercircuit 4402 may be configured to configured to perform maximum powerpoint tracking (MPPT) when charging the battery if the power source is asolar cell and/or solar panel. In some embodiments, battery controllercircuit 4402 includes circuits configured to perform slow charging (i.e.trickle charging) and/or fast charging. In some embodiments, thetemperature of the battery 4404 is monitored while fast charging isperformed so that the battery 4404 does not become damaged.

In some embodiments, the battery 4404 stores charge which can bereleased to power display device 4400. In some embodiments, batterycontroller circuit 4402 begins discharging battery 4404 when batterycontroller circuit detects that a wired power source of the displaydevice 4400 is removed (i.e. display device 4400 is removed from thewall). Battery 4404 may be any type or combination of batteries. In someembodiments, the battery is a nickel cadmium (Ni—Cd) battery and/or anickel-metal hydride (Ni-MH) battery. In various embodiments, thebattery is a lithium ion battery and/or a lithium polymer battery.

GPS 4406 may be configured to determine the location of the displaydevice 4400. In some embodiments, GPS 4406 determines the coordinates ofdisplay device 4400. GPS 4406 may send the coordinates of display device4400 to GPS controller 4410. In some embodiments, GPS controller 4410logs and tracks the location of display device 4400. In someembodiments, GPS controller 4410 is configured to determine whatdirection display device 4400 is moving by analyzing a plurality of GPScoordinate readings. Building map controller 4412 may contain some ofall of the functionality of building map controller 4304 as describedwith reference to FIG. 7. Building map controller 4412 may be configuredto provide a map of the building that display device 4400 is located into mobile directions controller 4416.

In some embodiments, mobile directions controller 4416 generates audiodirections and visual directions for display device 4400. Mobiledirections controller 4416 may be configured to provide audio directionsto audio controller 4240 as described with reference to FIGS. 6-7. Invarious embodiments, mobile directions controller 4416 may be configuredto provide visual direction to user interface controller 4242 asdescribed with reference to FIGS. 42-43. Mobile direction controller4416 may be configured to generate a display for user interface 4208. Insome embodiments, the display may be a map displaying the location ofdisplay device 4400 and a trace leading to the nearest exit.

In some embodiments, mobile directions controller 4416 may be configuredto determine directions based on the nature of the emergency determinedby emergency identifier 4218. For example, if there is a fire in thebuilding, the mobile directions controller 4416 may navigate the userholding the display device 4400 to the nearest accessible exit. If theemergency is an active shooter in the building, the display device maydirect the user holding display device 4400 to an exit and/or maynavigate the user holding display device 4400 to a room that can belocked and/or easily barricaded.

In some embodiments, audio controller 4240 is configured to use soundnavigation when appropriate. For example, if there is an active shooterin the building, audio controller 4240 may be configured to be silent sothat the shooter is not alerted of the location of the user holdingdisplay device 4400. In some embodiments, if there is a fire, smoke maybe thick enough and/or impair the vision of the user holding displaydevice 4400. Audio controller 4240 may be configured to play audiodirecting the user holding display device 4400 to an exit withoutneeding the user to be able to see user interface 4208.

Referring now to FIG. 45, a flow diagram of process 4500 forprioritizing directions for a display device is shown, according to anexemplary embodiment. In some embodiments, process 4500 is performed bydisplay device 4002, as described with reference to FIGS. 40-41. In step4502, display device 4002 receives emergency notifications from a BMS(e.g., building management system 4010.) In some embodiments, theemergency notification is a weather related notification (winter stormwatch, flooding, tornado warning, tornado watch, etc.). In someembodiments, the emergency notification is related to a buildingemergency (e.g., an active shooter in the building, unsafe water in thebuilding, structurally unsafe areas of the building, etc.)

In step 4504, display device 4002 receives weather related emergencynotifications from weather servers (e.g., weather server(s) 4008.) Thealert may be a winter storm watch, a flooding warning, a tornadowarning, a tornado watch, etc. In step 4506, display device 4002 mayreceive and/or query emergency sensors (e.g., building emergencysensor(s) 4006) for data indicating a building emergency. In someembodiments, the emergency sensors are configured to determine thenature of the emergency and provide an emergency notification directlyto the display device 4002. In some embodiments, the emergencynotification is one or a combination of a fire, a gas leak, unsafecarbon monoxide levels, etc. At step 4506, the display device 4002 mayalso access social media server(s) 4011 to receive and/or monitor dataindicating or relating to a building emergency.

The display device 4002 may thereby receive one or more data streamsthat include multiple messages indicating one or more emergenciesrelating to the building. The data streams may include a weather datastream indicating weather conditions associated with the building (i.e.,as received from weather server(s) 4008), a social media data streamindicating social media postings, comments, messages and/or otheractivity (i.e., as received from the social media server(s) 4011, a newsdata stream indicating one or more events associated with the building(e.g., as received from the social media server(s) 4011, the calendarapplication 4014, the user device 4012, the building management system4010, etc.), and/or other relevant data streams.

In step 4508, a decision is made by display device 4002 based on thepresence or absence of any emergencies. That is, based on the one ormore data streams received in steps 4502-4506, the display device 4002may determine an existence of an emergency and/or a nature or type ofthe emergency. If display device 4002 does not determine that there is abuilding and/or weather related emergency in step 4502, step 4504, andstep 4506, the display device 4300 may perform 4516 and displaynon-emergency related directions. If display device 4002 determines thatthere is a building and/or weather related emergency in step 4502, step4504 and/or step 4506 display device 4002 may prioritize the emergencydirections and display emergency related directions.

In step 4510, display device 4002 may prioritize all the emergenciesdetermined in step 4502, step 4504, and/or step 4506. Display device4002 may determine the priority of emergencies based on emergencyseverity and/or immediate impact to occupants of a building. Forexample, a winter storm warning may have a lower priority than an activeshooter.

In step 4512, display device 4002 may display the emergency directions.In some embodiments, the emergency directions are actions (e.g.,emergency response directions) to take in lieu of the building and/orweather related emergency. For example, if there is a tornado, thedirections may be to hide under desks and/or tables. If there is a fire,the display device 4002 may display evacuation directions and/or a routeto the nearest exit. If there are multiple emergencies present, thedisplay device 4002 may cycle emergencies and/or choose the mostimportant emergency to display. In some embodiments, display device 4002generates custom directions to accommodate the proper actions to takewhen there are multiple emergencies. For example, if there is a fire andan active shooter present in a building, display device 4002 may turnoff all sound on display device 4002 and display a message to theindividual to keep silent. The display device 4002 may then precede todirect building occupants to the nearest exits.

In step 4514, the display device 4002 may generate audible alarms. Insome embodiments, the audible alarm may be a loudspeaker messagedisclosing what the emergency is and/or the proper actions to take inlieu of the emergency. In some embodiments, the audible directions aredirections to the nearest exit. The directions may be “Turn left at theend of hallway and proceed to exit” and/or any other message indicatingthe proper directions that a user should take to evacuate the building.

If display device 4002 determines that no emergencies are present instep 4508, the display device may perform step 4516. In step 4516,display device 4002 receive user direction request via a user interface.In some embodiments, a user may input a specific conference room,meeting room, and/or office.

In step 4518, display device 4002 may identify an occupant based ondigital video processing from a camera, digital audio processing from amicrophone, and/or any other processing of occupancy sensors that can beused to identify a user. In some embodiments, display device 4002 storesfeatures of users that can be matched by using digital video processingand/or digital audio processing. In some embodiments, display device4002 sends a query with identified physical features of a user to abuilding management system (e.g., building management system 4010). Thebuilding management system may return the identity of the user. In someembodiments, the building management system may return a scheduleindicating locations and times of meetings which the user may berequired to attend, or which may be of interest to the user. In someembodiments, display device 4002 generates navigation direction based onthe identity of the user and/or based on the schedule received from thebuilding management system.

In step 4520, display device 4002 may generate directionsopportunistically. In some embodiments, directions may be based onevents occurring in the building. In some embodiments, display devicecommunicates with a building management system (e.g., buildingmanagement system 4010) and/or a building scheduler system. In someembodiments, display device 4002 generates opportunistic directionsbased on the location of display device 4002 in the building and/or theevents occurring in the building. In some embodiments, display device4002 communicates with the scheduling applications of mobile devices ofusers in the building and/or passing by display device 4002. In someembodiments, display device 4002 determines what events are occurring inthe building and their nature (e.g., public, private, etc.). In someembodiments, display device 4002 generates directions opportunisticallybased on the schedules of mobile devices in the building.

In some embodiments, display device 4002 prioritizes the directionsdetermined in steps 4516-4520 (step 4522). The directions can be rankedin order of highest priority. In some embodiments, requested directions(step 4516) may have the highest priority over opportunistic directions(step 4520) and/or direction determined based on information from anoccupancy sensor (step 4518). The ranking system may contain a queuewhich directions may be placed. The length of time which a direction isin the queue may factor into determining the priority for thatdirection. For example, if a conference advertisement is received from abuilding management system, the priority for displaying thisadvertisement may be low. In some embodiments, the priority of adirection may determine how long the direction is displayed on a userinterface of display device 4002. The highest priority direction may bedisplayed on a user interface of display device 4002.

Referring now to FIG. 46, a flow diagram of process 4600 for handing offdirections between display devices is shown, according to an exemplaryembodiment. In some embodiments, process 4600 is performed by displaydevice 4300, as described with reference to FIG. 43. Process 4600 mayinclude some or all of the steps of process 4500 as described withreference to FIG. 45. In step 4508, display device 4300 determines ifthere is an emergency present in the building in which display device4300 is located. If there is an emergency, steps 4510, 4512, and 4514are performed as described with reference to FIG. 45.

In step 4602, display device 4300 sends emergency directions to otherdisplay devices located in the building. In some embodiments, displaydevice 4300 determines where other display devices are located in thebuilding with a display device location controller (e.g., display devicelocation controller 4308). In some embodiments, display device 4300sends the emergency directions to other devices located in the buildingvia ad hoc communication (e.g., ad hoc Wi-Fi, ad hoc Zigbee, ad hocBluetooth, NFC etc.). In some embodiments, display device 4300 isconfigured to communicate ad hoc to the other display devices. Invarious embodiments, display device 4300 may be configured to transmitthe emergency directions to the other display devices via network 4004as described with reference to FIG. 40. In some embodiments, network4004 may connect display devices on multiple floors, multiple zones,multiple buildings, and multiple campuses. In some embodiments displaydevice 4300 may send emergency directions to display devices located ona different floor than the display device 4300, a different zone thanthe display device 4300, a different building than the display device4300, and a different campus than the display device 4300.

In step 4508, if no emergency is present, display device 4300 mayreceive direction requests from user interface (step 4604). In someembodiments, display device 4300 may be configured to allow users toenter destinations via a touch screen user interface. In someembodiments, the destination is a conference room, a meeting room,and/or an office. Display device 4300 may be configured to display anarrow, a map, turn by turn directions, and/or generate audio directions.Display device 4300 may determine other display devices along the routeto the destination (step 4608) and may send display directions to thesedevices ad hoc and/or over network 4004 (step 4610).

In step 4606, display device 4300 may determine directions for anoccupant based on the identity of the occupant. In some embodiments,display device 4300 uses at least one of a camera and/or a microphone todetermine the identity of an occupant. An occupancy controller (e.g.,occupancy controller 4238) may be configured to identify occupants basedon data received from occupancy sensors (e.g., cameras, microphones,etc.). Display device 4300 may be connected to a network (e.g., network4004) and may be able to retrieve meeting information associated withthe identified user. Display device 4300 may be configured to displaydirections (arrows, turn by turn directions, maps, etc.) based on anydestinations that are indicated by the identified user's meetingschedule. In some embodiments, display device 4300 is configured todetermine other display devices along the route to the destination (step4608) and may send display directions to these devices ad hoc and/orover network 4004 (step 4610).

Referring now to FIG. 47, a flow diagram of process 4700 for removing adisplay device from a wall and using it as a map in an emergencysituation, according to an exemplary embodiment. In some embodiments,process 4700 is performed by display device 4400, as described withreference to FIG. 44. In step 4702, display device 4400 determines ifthere is an emergency present in the building in which display device4400 is located. In step 4706, display device 4400 determines if thereis a building emergency as determined by steps 4502, 4504, and 4506, asdescribed with reference to FIG. 45. If there is no building and/orweather related emergency, display device 4400 may resume normaloperation (e.g., 4704). In some embodiments, normal operation isreceiving environmental setpoints via user interface 4208 and regulatingenvironmental conditions of zones and/or a building (e.g., building 10)with HVAC controller 4226. In some embodiments, normal operation iswaiting for an emergency message to be received such as in steps 4502,4504, and 4506 as described with reference to FIG. 45.

In some embodiments, if an emergency is determined in at least one ofsteps 4502, 4504, and 4506 as described with reference to FIG. 45,display device 4400 displays emergency situation directions (step 4706).In some embodiments, the emergency situation directions are evacuationdirections, phone numbers to call, an appropriate course of action totake, etc. In step 4708, display device 4400 may generate an alarm. Insome embodiments, the alarm is a siren, a building-wide message, and/orany other audible alarm.

In step 4710, display device 4400 may prompt a user to remove displaydevice 4400 from the wall. In some embodiments, user interface 4208intermittently periodically displays a message “Remove From Wall ForEvacuation” for a predefined duration of time. In some embodiments, theuser may press a button on user interface 4208 which confirms that theuser has removed the device from the wall. In some embodiments, displaydevice 4400 may use GPS 4406 and GPS controller 4410 to determine thatdisplay device 4400 has is changing location and has been removed fromits original location. In some embodiments, display device 4400 has asensor such as a switch which detects that the device has been removedfrom the wall.

In step 4712, display device 4400 may determine its current locationwith GPS 4406. In some embodiments, GPS controller 4410 may communicatewith GPS 4406 to determine coordinates of display device 4400. In someembodiments, the coordinates are a latitude, a longitude, and analtitude. Display device 4400 may be configured to use the coordinatesto determine the location of the display device 4400 and the user whohas removed display device 4400 from the wall in the building. In someembodiments, display device 4400 uses GPS controller 4410 to poll GPS4406 for coordinates periodically. In some embodiments, GPS controller4410 receives a new coordinate when one of the coordinates (i.e.,altitude, longitude, and latitude) has changed more than a predefinedamount.

In step 4714, the display device may use building map controller 4412and mobile directions controller 4416 to determine a route to anevacuation point and/or a safe zone with the GPS coordinates of GPScontroller 4410. In some embodiments, user interface controller 4242 maydisplay the location of the user on user interface 4208 and a map with aroute indicating the necessary directions to take to reach theevacuation point and/or safe zone.

Referring now to FIG. 48, a drawing 4800 of an emergency display fordisplay device 4002 is shown, according to an exemplary embodiment. Insome embodiments, display device 4002 is configured to display emergencydirections on user interface 4208. Emergency directions 4802 displaytext based directions for exiting a building. In some embodiments, thedirections may be map based. Map based directions may allow anindividual to see their current location on a map and a route to thenearest exit, evacuation zone, and/or safe zone. Audio 4804 may bebroadcast by display device 4002 to accompany the visual emergencymessage. In some embodiments audio 4804 is broadcast via speaker 4206.The emergency audio, audio 4804, may give audible directions tooccupants of the building to evacuate. In some embodiments, audio 4804may give occupants of the buildings evacuation directions and/ordirections to a safe zone.

Referring now to FIG. 49, a drawing 4900 of an opportunistic display fordisplay device 4002 is shown, according to an exemplary embodiment. Insome embodiments, the opportunistic message may be a message generatedand/or determined by opportunistic controller 4230 as described withreference to FIGS. 42-44. In some embodiments, display device 4002 isconfigured to display opportunistic messages and opportunisticdirections on user interface 4208. Opportunistic message 4902 displaysadvertise a building event and display directions to said buildingevent. The advertisement may include a logo, the location of an event, acost of an event, and/or any other information that could be used in theadvertisement. Audio 4904 may be broadcast by display device 4002 toaccompany the opportunistic message. In some embodiments audio 4804 isbroadcast via speaker 4206. The opportunistic audio message, audio 4804,may give audible directions to occupants of the building to report tocertain rooms, floors, building, and/or any other location. In someembodiments, audio 4904 is music and/or any other audio based message orsound.

Referring now to FIG. 50, a drawing 5000 of a route notification 5002for display device 4002 and/or display device 4300 is shown, accordingto an exemplary embodiment. In some embodiments, display device 4002and/or display device 4300 is configured to display directions on userinterface 4208. In some embodiments, the directions are for anidentified and/or tracked occupant. Route notification 5002 may includethe name of the occupant being given directions. In some embodiments,route notification 5002 includes a route destination (e.g., “WestConference room in Building 4, on Floor 4”). Further, directions may begiven to the occupant. The directions may be the appropriate turns totake to reach a location (e.g., “follow hallway to end and make leftturn”).

In some embodiments, audio 5004 may be broadcast by display device 4002and/or display device 4300 to accompany the direction message 5102. Insome embodiments audio 5004 is broadcast via speaker 4206. The audio5104 may give audible directions to occupants of the building to reportto certain rooms, floors, building, and/or any other location. In someembodiments, audio 5004 is music and/or any other audio based message orsound. Audio 5004 may identify an occupant by name and/or handle beforeplaying directions for the occupant.

Referring now to FIG. 51, a drawing 5100 of an alternate routenotification for display device 4002 and/or display device 4300 isshown, according to an exemplary embodiment. In some embodiments,display device 4002 and/or display device 4300 is configured to displayalternate route directions on user interface 4208. In some embodiments,the directions are for an identified and/or tracked occupant. In someembodiments, the identified and/or tracked occupant has a knowndisability. Alternate route message 5102 may give directions to anoccupant of an alternate route based on the disability of the occupant.For example, the route may direct an occupant to a wheelchair rampinstead of a staircase if the identified occupant has crutches, awheelchair, and/or any other disability prohibiting the occupant fromascending and/or descending stairs.

In some embodiments, audio 5104 may be broadcast by display device 4002and/or display device 4300 to accompany the alternate route message5102. In some embodiments audio 5104 is broadcast via speaker 4206. Theaudio 5104 may give audible directions to occupants of alternate routes.In some embodiments, the audio 5104 may direct an occupant to awheelchair accessible ramp. In some embodiments, audio 5104 is musicand/or any other audio based message or sound. Audio 5104 may identifyan occupant by name and/or handle before playing directions for thealternate route.

Referring now to FIG. 52, a drawing 5200 of another alternate routenotification for display device 4002 and/or display device 4300 isshown, according to an exemplary embodiment. In the embodiment shown,display device 4002 (and/or display device 4300 and/or display device4400) is configured to display an arrow 5202 that points in a directionthat a user/occupant of the building should move to avoid an emergency.More particularly, in the example shown, the arrow 5202 points away froma location of an active shooter detected by the building emergencysensor(s) 4006. In such an example, the display device 4002 determines aroute based on a location of the active shooter and a building map orfloorplan to determine a safe direction for an occupant to travel. Thearrow 5202 thereby directs the occupant in a safe direction (e.g., awayfrom danger). In some embodiments, the arrow 5202 may be updated topoint in various directions in real time as the location of the activeshooter detected by the building emergency sensor(s) 4006 changes. Thedisplay device 4002 and/or display device 4300 thereby facilitates auser in fleeing an active shooter.

More particularly, in the example of FIG. 52, the processing circuit4210 of the display device 4002 may receive, via the communicationsinterface 4202, a first indication of a first location of a shooter froma shot detection system. The shot detection system may be included withthe building emergency sensors 4006 and may be configured to detect agunshot in the building and determine a location of the gunshot in thebuilding. The processing circuit 4210 may determine and escape route, anevacuation route, or other route to safety based on the first locationof the shooter, the location of the display device 4002, and thelocation of one or more additional display devices (e.g., display device4016, display device 4018), and a floor plan of the building, A firstnavigation direction may be displayed on the display device 4002 (e.g.,as shown in FIG. 52) to direct a user along a route that avoids theshooter within the building. A second navigation direction may bedisplayed on a second display device (e.g., display device 4016, displaydevice 4018) to show a user a next step on the safe route to avoid theshooter.

In some cases, the shooter may move within the building. The shotdetection system may detect a second location of a gunshot and providethe second location to the display device 4002. The display device maythen update the escape route and the associated navigations directionson the display device 4002 and on the one or more additional displaydevices (e.g., display device 4016, display device 4018) to direct theuser along an update route that avoids the second location. The user maythereby be guided to safety along a route that avoids the active shooterin the building. For example, with reference to FIG. 52, the arrow 14202may be updated to point in a new direction (e.g., switched from pointingright to pointing left) when the gunman is detected as relocating to theright of the display device 4002.

Halo Light Emitting Diode (LED) System

A display device includes a housing having a front portion, a rearportion, and a halo having a rim which is disposed between the frontportion and the rear portion, according to some embodiments. In someembodiments, the halo receives light emitted by one or more LEDs anddiffuses the light along sides of the display device. The halo includesmultiple light guiding portions which each have a receiving post and asweep portion, according to some embodiments. In some embodiments, eachof the light guiding portions protrude from a rim of the halo which ispositioned between the front portion and rear portion of the displaydevice. In some embodiments, the halo is made of or includes atranslucent material and/or a transparent material. In some embodiments,the LEDs are disposed along a path of an LED board and are eachconfigured to emit light received by a corresponding light guidingportion. In some embodiments, the light guiding portions are cantileverportions, having an overall S-shape, protruding at one end from the rim.In some embodiments, the light guiding portions include exteriorsurfaces coated (e.g., cladded) with an opaque material which does notallow light to pass through along substantially an entire length of thelight guiding portions. In some embodiments, a surface of the receivingposts and an exterior surface of the rim does not include the opaquematerial, such that light may enter and exit the light guiding portionsonly at the receiving post and exterior surface of the rim,respectively.

In some embodiments, the halo facilitates notification of a userregarding any of information, a message, an event, etc., at a widerviewing angle. For example, if the user is not positioned directly infront of the display device, the user may be unable to view a frontdisplay panel of the display device, according to some embodiments. Insome embodiments, the halo directs light outwards from sides of thedisplay device, so that the light emitted by the LEDs can be viewed by auser at a generally side angle.

In some embodiments, the display device is a thermostat, e.g., thecontrol device 214 as described with reference to FIGS. 2-39. In someembodiments, the display device is the display device 4002 as describedwith reference to FIGS. 40-52. In some embodiments, the display deviceis configured to receive information from any of a sensor, anothercontroller, a network, etc. as described herein. In some embodiments,the display device is configured to patterningly adjust an operation ofone or more of the LEDs (e.g., which LEDs switch on/off, when certainLEDs switch on/off, a brightness of one or more of the LEDs, a color ofone or more of the LEDs, etc.) to provide unique visual notifications tothe user. In some embodiments, the display device includes a controllerconfigured to determine patterned operations of the LEDs to produce theunique visual notifications. In some embodiments, the display device isa general display device and may be used for a variety of applications(e.g., building systems, security systems, reminder systems, emergencyexit systems, fire alarm systems, indoor air quality systems, automotivesystems, alarm systems, intrusion detection systems, etc.).

Advantageously, the display device facilitates visual notificationregarding a variable, an event, a change in a variable, etc., to a userat a wider viewing angle, according to some embodiments.

Referring now to FIG. 53, display device 5300 is shown, according tosome embodiments. Display device 5300 may be control device 214 asdescribed with reference to FIGS. 2-39 and/or the display device 4002 asdescribed with reference to FIGS. 40-52 and can include any and/or allof the components and/or be configured to perform any of the operationsof control device 214 and/or the display device 4002. For example, thevisual notifications described with reference to control device 214 canbe implemented via the LED halo of display device 5300. Display device5300 is shown to include a front 5318, a left side 5314, a right side5316, a top 5312, a bottom 5320, and a rear 5326, according to someembodiments. In some embodiments, display device 5300 is configured tobe a wall-mounted display device. In some embodiments, display device5300 includes a mounting portion configured to mount display device 5300to a wall. In some embodiments, display device 5300 is configured to beat least partially received by the wall. In some embodiments, displaydevice 5300 includes a flat portion configured to facilitate mounting ofdisplay device 5300. In some embodiments, display device 5300 isconfigured to sit (e.g., rest, lay, be adjacent to, etc.) a surface(e.g., a face, a table, a top surface of equipment, etc.). In someembodiments, display device 5300 is configured to display any of sensorinformation, equipment information, controller information, messages,alerts, etc., shown as display information 5324, to a user. Displaydevice 5300 is configured to facilitate an alert or a message to a userbased on information received from any of equipment, a controller, asensor, a remote server, etc., according to some embodiments. In someembodiments, display device 5300 is configured to provide an alert to auser via user interface 5306. In some embodiments, user interface 5306is or includes any of an LCD screen, an LED screen, a resistive touchscreen, a surface capacitive touch screen, a projected capacitive touchscreen, a surface acoustic wave touch screen, an infrared touch screen,etc. In some embodiments, user interface 5306 includes one or morebuttons. In some embodiments, user interface 5306 is configured toreceive an input from a user (e.g., through any of a touchscreen, one ormore buttons, a wireless device, etc.) and provide the input to any of acontroller, equipment, etc. In some embodiments, the input adjusts adisplay of user interface 5306. For example, the input may indicate anadjustment of an LEDs (e.g., brightness, color, pattern, etc.), ofdisplay device 5300, according to some embodiments. In some embodiments,the input adjusts information, alerts, data, etc., displayed by userinterface 5306. For example, the input from the user may transition userinterface 5306 from displaying a first message (e.g., a time of day) todisplaying a second message (e.g., a date), according to someembodiments. In some embodiments, user interface 5306 displays one ormore environmental conditions (e.g., temperature, pressure, indoor airquality, etc.) of a space. In some embodiments, the space which userinterface 5306 displays information regarding is a space within whichdisplay device 5300 is positioned. In some embodiments, the space whichuser interface 5306 displays information regarding is another spacewhich display device 5300 is not positioned within. In some embodiments,user interface 5306 displays one or more environmental conditions of oneor more spaces (e.g., the space which display device 5300 is positionedwithin, a second space, a third space, etc.). In some embodiments, userinterface 5306 displays information (e.g., environmental conditioninformation) regarding various rooms of a building.

In some embodiments, user interface 5306 transitions between a set ofpredetermined messages/alerts/information. For example, user interface5306 may iteratively display an indoor air temperature, an indoor airquality, an outdoor air temperature, a time of day, an alert, etc. Insome embodiments, user interface 5306 transitions from displaying onemessage/information/alert at an end of a predetermined time period. Forexample, user interface 5306 may display a differentmessage/information/alert every 1 second, every 5 seconds, etc., upon arequest received from the user through user interface 5306, or upon anevent (e.g., an alert), according to some embodiments.

Display device 5300 includes a front portion 5302 and a rear portion5304, according to some embodiments. In some embodiments, front portion5302 and rear portion 5304 are coupled (e.g., removably coupled, fixedlycoupled, selectively coupled, fastened, integrally formed, etc.) to eachother. In some embodiments, front portion 5302 and rear portion 5304 areremovably coupled (e.g., by fasteners). In some embodiments, frontportion 5302 and rear portion 5304 are configured to interface with eachother (e.g., a slip fit, a frictional fit, a snap fit, etc.). In someembodiments, front portion 5302 and rear portion 5304 use a combinationof fasteners and an interfaced fit (e.g., a slip fit, a frictional fit,a snap fit, etc.).

In some embodiments, front portion 5302 includes user interface 5306. Insome embodiments, front portion 5302 includes an aperture (e.g., anopening, a hole, a recess, etc.) configured to receive user interface5306 therein. In some embodiments, front portion 5302 includes acovering 5310 configured to interface with front portion 5302. In someembodiments, covering 5310 is a protective covering configured toprotect user interface 5306 from damage. In some embodiments, covering5310 is disposed in front of user interface 5306. Covering 5310 may beany of a glass material, a plastic material, etc. In some embodiments,covering 5310 is translucent. In some embodiments, covering 5310 istransparent. In some embodiments, covering 5310 is configured to allowlight emitted by user interface 5306 to pass through.

Covering 5310 is disposed outside of front portion 5302, according tosome embodiments. In some embodiments, covering 5310 is disposedadjacent an inner surface of front portion 5302. In some embodiments,covering 5310 covers at least part of or an entire area of the apertureof front portion 5302 which receives user interface 5306. In someembodiments, covering 5310 is received in an aperture (e.g., an opening,a hole, a recess, etc.) of front portion 5302. In some embodiments,covering 5310 is received within the aperture within which userinterface 5306 is received.

In some embodiments, sides 5308 (e.g., walls, borders, faces, surfaces,panels, etc.) are disposed between front portion 5302 and rear portion5304. In some embodiments, sides 5308 extend between rear portion 5304and front portion 5302. In some embodiments, any of sides 5308 areintegrally formed with at one of front portion 5302 and rear portion5304. For example, in some embodiments, sides 5308 are integrally formedwith front portion 5302. In some embodiments, sides 5308 are integrallyformed with rear portion 5304. In some embodiments, one or more of sides5308 are integrally formed with one of front portion 5302 or rearportion 5304, while one or more other sides 5308 are integrally formedwith another of front portion 5302 or rear portion 5304. For example,left side 5308 a and right side 5308 b are integrally formed with frontportion 5302 and upper side 5308 c and bottom side 5308 d are integrallyformed with rear portion 5304 (or vice versa), according to someembodiments.

In some embodiments, sides 5308 are coupled (e.g., removably coupled,attached, fastened, fixed, slip fit, frictionally fit, snap fit, etc.)to at least one of front portion 5302 and rear portion 5304. In someembodiments, sides 5308, front portion 5302, and rear portion 5304define an enclosure having an inner volume therein. In some embodiments,any of user interface 5306, a controller, a power circuit, etc., or anyother components, subcomponents or devices (e.g., LEDs) are disposedwithin the inner volume defined by front portion 5302, rear portion 5304and sides 5308.

In some embodiments, sides 5308 are generally planar. For example, asshown in FIG. 53, sides 5308 are generally flat surfaces extendingbetween front portion 5302 and rear portion 5304, according to someembodiments. In some embodiments, sides 5308 are slanted at an angle. Insome embodiments, sides 5308 have an arcuate curvature. In someembodiments, sides 5308 are generally curved and have a non-constantradius of curvature.

Opposite sides 5308 are substantially parallel to each other, accordingto some embodiments. For example, left side 5308 a is shown generallyparallel to right side 5308 b and upper side 5308 c is generallyparallel to bottom side 5308 d, according to some embodiments. In someembodiments, opposite sides 5308 are not parallel to each other. Forexample, in some embodiments, left side 5308 a non-parallel with rightside 5308 b. In some embodiments, adjacent sides 5308 are substantiallyperpendicular to each other. For example, as shown in FIG. 53, left side5308 a is substantially perpendicular to upper side 5308 c (which isadjacent left side 5308 a), according to some embodiments. In someembodiments, left side 5308 a is substantially perpendicular to bottomside 5308 d. In some embodiments, left side 5308 a, right side 5308 b,upper side 5308 c, and bottom side 5308 d are integrally formed witheach other.

In some embodiments, a halo 5322 is positioned between front portion5302 and rear portion 5304. In some embodiments, halo 5322 is positionedbetween sides 5308 and one of front portion 5302 and rear portion 5304.For example, as shown in FIG. 1, sides 5308 are integrally formed withrear portion 5304, and halo 5322 is positioned between rear portion5304/sides 5308 and front portion 5302, according to some embodiments.In some embodiments, halo 5322 is configured to any of diffuse, direct,guide, focus, scatter, etc., light emitted by one or more LEDs. In someembodiments, halo 5322 facilitates light emission, diffusion, direction,guidance, focusing, scattering, outwards along and/or outwards fromdisplay device 5300. For example, in some embodiments, halo 5322diffuses light emitted by one or more LEDs in one or more directionsgenerally normal to sides 5308. In some embodiments, halo 5322facilitates a wider viewing angle of the light emitted by the one ormore LEDs to provide an alert to an observer.

Referring now to FIGS. 54-56, display device 5300 is shown in greaterdetail, according to some embodiments. In some embodiments, displaydevice 5300 has an overall height 5402. In some embodiments, an overallheight of front portion 5302 is substantially equal to height 5402. Insome embodiments, height 5402 is a distance from a bottom-most edge(e.g., bottom side 5308 d) and an upper-most edge (e.g., upper side 5308c). In some embodiments, height 5402 is an average height of displaydevice 5300. In some embodiments, display device 5300 includes a bezel(e.g., a rim, a retainer, etc.), shown as bezel 5418. In someembodiments, bezel 5418 extends substantially an entire perimeter offront portion 5302.

Rear portion 5304 is shown to include a first modular portion 5414 and asecond modular portion 5416, according to some embodiments. In someembodiments, first modular portion 5414 and second modular portion 5416are integrally formed. In some embodiments, first modular portion 5414and second modular portion 5416 define rear portion 5304. First modularportion 5414 is shown to have an overall height substantially equal toheight 5402, according to some embodiments. In some embodiments, firstmodular portion 5414 includes and/or is sides 5308. In some embodiments,first modular portion 5414 is configured to interface with one or moreof sides 5308 and front portion 5302. For example, first modular portion5414 is configured to interface with sides 5308 and/or front portion5302 with at least one of a slip fit, a frictional fit, a snap fit,fasteners, etc., according to some embodiments.

In some embodiments, second modular portion 5416 has a height 5410 anddepth 5408. Height 5410 is shown less than overall height 5402 ofdisplay device 5300, according to some embodiments. In some embodiments,height 5410 is substantially equal to or greater than overall height5402. In some embodiments, second modular portion 5416 protrudes (e.g.,extends, juts from, extrudes from, etc.), surface 5506 of first modularportion 5414. In some embodiments, second modular portion 5416 protrudesa distance from surface 5506 substantially equal to depth 5408.Advantageously, if display device 5300 is a wall-mounted display device,second modular portion 5416 is configured to extend within and bereceived by an aperture of the wall, according to some embodiments. Insome embodiments, second modular portion 5416 extends at least partiallywithin an aperture of a wall. In some embodiments, first modular portion5414 extends at least partially within an aperture of a wall. Forexample, in some embodiments, the aperture (e.g., of the wall) is arecess (e.g., cavity, indent) which is stepped to both receive firstmodular portion 5414 and at least partially receive second modularportion 5416. In some embodiments, second modular portion 5416 extendsfrom surface 5506 of first modular portion 5414 which is disposedsub-flush a rim 5518 of first modular portion 5414. In some embodiments,rim 5518 is cooperatively formed by sides 5308. In some embodiments, rim5518 extends along an entire perimeter of first modular portion 5414. Insome embodiments, rim 5518, surface 5506, and sides 5512 of secondmodular portion define a recess 5600 having a width 5520 which runsalong an entire perimeter of display device first modular portion 5414.In some embodiments, recess 5600 is configured to interface with aprotrusion of a mounting plate (e.g., a wall mounting plate, a wall,etc.).

In some embodiments, first modular portion 5414 includes one or morefastener elements (e.g., posts, apertures, threaded bores, clips,latches, etc. configured to fasten display device 5300 to a wall), shownas fastener elements 5508. Fastener elements 5508 are shown as boresconfigured to receive a fastener to removably couple display device 5300to a surface. In some embodiments, fastener elements 5508 are threadedbores. In some embodiments, fastener elements 5508 are bores configuredto receive self-tapping screws. In some embodiments, fastener elements5508 are disposed along a patterned path. In some embodiments, fastenerelements 5508 are disposed proximate corners of display device 5300. Insome embodiments, fastener elements 5508 are evenly spaced a distanceapart.

In some embodiments, second modular portion 5416 is generallyrectangular having sides (e.g., walls, panels, sidewalls, etc.), shownas sides 5512. In some embodiments, second modular portion 5416 is agenerally rectangular shape having a length 5504 and a height 5410. Insome embodiments, adjacent sides 5512 form a rounded intersection point.For example, side 5512 c and side 5512 a are adjacent each other, andintersect to form a fillet. In some embodiments, second modular portion5416 is a generally rectangular shape having filleted (e.g., rounded)corners. In some embodiments, second modular portion 5416 is a generallyrectangular shape having chamfered corners. In some embodiments, firstmodular portion 5414 is generally rectangular shaped having height 5402and length 5502. In some embodiments, first modular portion 5414 isgenerally rectangular shaped having filleted corners (e.g., corners5510). In some embodiments, first modular portion 5414 is generallyrectangular shaped having chamfered corners. In some embodiments, acenter of a cross section of first modular portion 5414 is substantiallycoincident with a center of a cross section of second modular portion5416.

In some embodiments, second modular portion 5416 includes a surface(e.g., a back surface, a back plate, a back panel, a back wall, etc.),shown as rear surface 5514. In some embodiments, rear surface 5514includes any of fastener elements 5508. In some embodiments, rearsurface 5514 includes one or more apertures (e.g., bores, openings,through-holes, rectangular openings, etc.), configured to facilitatewired connections to a controller (e.g., a processing circuit, a powerboard, etc.) disposed within display device 5300. In some embodiments,rear surface 5514 is removably connected to sides 5512, facilitatingeasy access to internal components of display device 5300. In someembodiments, rear surface 5514 is removably connected to sides 5512 withany one of or a combination of fasteners, a slip fit, a frictional fit,a snap fit, etc. In some embodiments, rear surface 5514 is configured tobe received by an aperture cooperatively formed by sides 5512.

In some embodiments, surface 5506 of first modular portion 5414 includesa rectangular aperture (e.g., opening, recess, hole, etc.), shown asrectangular opening 5516. In some embodiments, rectangular opening 5516is configured to receive a protrusion of another member (e.g., amounting plate, a wall, etc.) to connect display device 5300 to theother member. In some embodiments, rectangular opening 5516 isconfigured to allow a wired connection (e.g., a USB connection, a powerconnection, etc.) to a controller disposed within display device 5300.In some embodiments, one or more rectangular openings 5516 are includedon rear surface 5514.

Referring now to FIGS. 57-59, various configurations display device 5300are shown, according to some embodiments. Referring now to FIG. 57display device 5300 is shown according to FIGS. 53-56, according to someembodiments. In some embodiments, display device 5300 includes frontportion 5302 and rear portion 5304 which couple with each other. Frontportion 5302 is shown having an overall rectangular shape with length(e.g., length 5502) greater than length (e.g., length 5504) of rearportion 5304, according to some embodiments.

Referring now to FIG. 58, display device 5300 is shown having rearportion 5304 substantially equal in length to length of front portion5302, according to some embodiments. In some embodiments, rear portion5304 is generally rectangular shaped.

Referring now to FIG. 59, display device 5300 is shown including a rearportion 5304 which is generally curved, according to some embodiments.In some embodiments, rear portion 5304 includes a mounting plate 5902configured to facilitate mounting of display device 5300 to a surface(e.g., a wall). In some embodiments, mounting plate 5902 is integrallyformed with rear portion 5304. In some embodiments, mounting plate 5902includes a flat rear surface configured to interface with the flatsurface. In some embodiments, mounting plate 5902 includes one or morefastener elements (e.g., screws, clips, hangers, etc.), configured toremovably couple mounting plate 5902 with the surface.

Referring now to FIGS. 60 and 61, front portion 5302 is shown in greaterdetail, according to some embodiments. In some embodiments, frontportion 5302 is configured to couple (e.g., removably, etc.) with acontroller 6002 (e.g., a processing circuit). In some embodiments,controller 6002 is configured to control an operation of user interface5306. In some embodiments, controller 6002 is configured to removablycouple with front portion 5302 with one or more retaining clips 6006(e.g., snap clips, latches, etc.). In some embodiments, retaining clips6006 protrude from front portion 5302 and are configured to interfacewith an edge of controller 6002. In some embodiments, controller 6002includes one or more notches 6008 (e.g., recessions, grooves, etc.)configured to facilitate coupling between controller 6002 and frontportion 5302. In some embodiments, notches 6008 provide an edge withwhich retaining clips 6006 interface.

Referring still to FIGS. 60 and 61, front portion 5302 is shown toinclude posts 6004, according to some embodiments. In some embodiments,posts 6004 extend from front portion 5302. In some embodiments, posts6004 provide a surface to which controller 6002 is adjacent. In someembodiments posts 6004 include a bore configured to interface with afastener. For example, the bore is a threaded bore, according to someembodiments. In some embodiments, one or more of posts 6004 extend to asurface or a corresponding post of rear portion 5304. In someembodiments, posts 6004 extend from a back surface of front portion5302. In some embodiments, bezel 5418 retains at least one of userinterface 5306 or covering 5310 in position.

Referring now to FIG. 62, front portion 5302 is shown without userinterface 5306 and covering 5310 assembled, according to someembodiments. In some embodiments, front portion 5302 includes a firstsurface 6210 and a second surface 6208. In some embodiments, secondsurface 6208 is offset a distance relative to surface 6210 such thatsecond surface 6208 offset the distance relative to surface 6210 definesa recess (e.g., an indent, an aperture, etc.), shown as recess 6212. Insome embodiments, recess 6212 is configured to receive user interface5306. In some embodiments, second surface 6208 includes one or moreapertures (e.g., openings, holes, etc.), shown as rectangular apertures6202. In some embodiments, rectangular apertures 6202 facilitate wiredconnection between user interface 5306 and a controller. In someembodiments, rectangular apertures 6202 facilitate removable connectionbetween user interface 5306 and front portion 5302.

In some embodiments, recess 6212 is generally rectangular. Recess 6212is shown to include an aperture (e.g., opening, hole, etc.), shown asvertical aperture 6206, according to some embodiments. In someembodiments, vertical aperture 6206 is a notch and extends partiallyalong a height of second surface 6208. In some embodiments, frontportion 5302 includes one or more apertures, shown as apertures 6204. Insome embodiments, apertures 6204 are rectangular and extend at leastpartially into first surface 6210.

Referring now to FIG. 63, rear portion 5304 is shown in greater detail,according to some embodiments. Rear portion 5304 includes an LED board6302 (e.g., a processing circuit, a controller, a PCB board, etc.)disposed within an inner volume 6308 of second modular portion 5416,according to some embodiments. In some embodiments, LED board 6302 isdisposed within an inner volume 6310 of first modular portion 5414. LEDboard 6302 is shown to include light emitting devices, shown as LEDs6304, according to some embodiments. In some embodiments, LEDs 6304 areconfigured to emit light which is directed through halo 5322 and emitsfrom a side of display device 5300. In some embodiments, LED board 6302is communicably connected with controller 6002.

Referring still to FIG. 63, rear portion 5304 is shown to include matingposts 6306, according to some embodiments. In some embodiments, matingposts 6306 are configured to interface (e.g., be adjacent to) a surfaceof front portion 5302. In some embodiments, mating posts 6306 facilitateremovable connection between front portion 5302 and rear portion 5304.

LED Board

Referring now to FIGS. 64 and 65, LED board 6302 is shown in greaterdetail, according to some embodiments. FIG. 64 shows LEDs 6400 disposedalong path 6406, according to some embodiments. Path 6406 is generallyrectangular, according to some embodiments. In some embodiments, path6406 is generally elliptical, generally square, etc., or any othergeometric shape. In some embodiments, LEDs 6400 are spaced non-evenlyalong path 6406. For example, as shown in FIG. 64, LED 6400 a isdisposed a distance 6402 from adjacent LED 6400 b along path 6406, whileLED 6400 g is disposed a distance 6408 from adjacent LED 6400 f alongpath 6406, according to some embodiments. In some embodiments, LEDs 6400are placed along path 6406 based on a desired function of display device5300. In some embodiments, LEDs 6400 are light emitting diodes. In someembodiments, LEDs 6400 are multi-color LEDs (e.g., red-green-blue (RGB)LEDs). In some embodiments, LEDs 6400 are single color LEDs (e.g., whiteLEDs). In some embodiments, LEDs 6400 are dimmable LEDs (e.g.,brightness can be adjusted, intensity of emitted light can be adjusted,etc.). In some embodiments, LEDs 6400 receive signals through LED board6302 to cause LEDs 6400 to adjust a brightness of one or more of LEDs6400. In some embodiments, LEDs 6400 receive signals through LED board6302 to cause LEDs 6400 to switch from an on-state to an off-state. Insome embodiments, LEDs 6400 receive signals through LED board 6302 toadjust a color of one or more of LEDs 6400. Any of the brightness,on/off state, color, etc., of any of LEDs 6400 is adjusted according toone or more predetermined patterns, according to some embodiments. Forexample, in some embodiments, certain LEDs 6400 (e.g., LEDs 6400 a-c)are actuated between an on-state and an off-state for a predeterminedamount of time (e.g., on for 5 seconds, off for 4 seconds, etc.) whileother LEDs 6400 (e.g., LEDs 6400 d-i) are not actuated between anon-state and an off-state. Any of the dimming, color, etc., of o any ofLEDs 6400 is configured to operate according to a similar pattern, or acombination of patterns thereof.

As shown in FIG. 64, LED board 6302 includes nine LEDs 6400, accordingto some embodiments. In some embodiments, LED board 6302 includes moreor less than nine LEDs 6400.

FIG. 65 shows LEDs 6400 equally spaced along path 6406, according tosome embodiments. For example, LED 6400 a is shown spaced a distance6500 along path 6406 from LED 6400 b, according to some embodiments. Insome embodiments, each of LEDs 6400 are spaced distance 6500 along path6406 relative to a neighboring LED 6400. For example, LEDs 6400 a-b arespaced distance 6500 apart along path 6406, and LEDs 6400 b-c are alsospaced distance 6500 apart along path 6406, according to someembodiments. In some embodiments, one or more of LEDs 6400 are offsetrelative to path 6406. For example, LED 6400 a is offset a predeterminedamount from path 6406, according to some embodiments. In someembodiments, each of LEDs 6400 are proximate a portion of halo 5322.

Halo

Referring now to FIGS. 66-71, halo 5322 is shown in greater detail,according to some embodiments. In some embodiments, halo 5322 isconfigured to receive light emitted by any of LEDs 6400 and direct,diffuse, scatter, etc., the emitted light along at least one of sides5308. In some embodiments, halo 5322 is configured to produce a glowalong at least one of sides 5308. Since LEDs 6400 can be configured tooperate in a patterned manner (e.g., on-state, off-state, brightness,color, etc.), halo 5322 may diffuse, direct, scatter, etc., the emittedlight along at least one of sides 5308 according to a currently usedpattern, according to some embodiments. In some embodiments, halo 5322facilitates a glow along sides 5308 of display device 5300. In someembodiments, halo 5322 facilitates indicating a message to a user (e.g.,a particular pattern represents and/or corresponds to a particularevent). In some embodiments, halo 5322 facilitates a wider off-axisviewing angle of the message. For example, in some embodiments, displaydevice 5300 is a thermostat. In some embodiments, LEDs 6400 maytransition between a blue color and a red color which corresponds to theindoor air temperature of the conditioned space. In some embodiments,the blue color indicates a low temperature, and the red color indicatesa high temperature. In some embodiments, a wavelength (A) of lightemitted by LEDs 6400 and directed by halo 5322 is dependent on thetemperature. In some embodiments, LEDs 6400 emit light at any wavelength(A) within the visible spectrum of light. Advantageously, thisfacilitates notifying a user or an occupant of the conditioned spacewithout the user/occupant necessarily being able to observe userinterface 5306, according to some embodiments. For example, if a user isnot in front of display device 5300 such that the user can observe userinterface 5306 directly, the user may still be notified of a changingtemperature (or any other variable) of the conditioned space byobserving the light emitted from display device 5300 by halo 5322.

In some embodiments, halo 5322 is or includes translucent and/ortransparent material. In some embodiments, halo 5322 is configured toallow light to pass through. In some embodiments, one or more exteriorsurfaces of halo 5322 are coated with a material which does not allowlight to pass through. For example, in some embodiments, all exteriorsurfaces of halo 5322 are coated with a material (e.g., a coating, apaint, etc.)

Referring to FIG. 66, in some embodiments, at least a portion of halo5322 is positioned between front portion 5302 and rear portion 5304. Insome embodiments, at least a portion of halo 5322 is positioned adjacentfront portion 5302 at a first side and adjacent rear portion 5304 at anopposite site. In some embodiments, at least a portion of halo 5322 isadjacent bezel 5418.

Referring still to FIG. 66, an outer edge of halo 5322 is shown angledrelative to a horizontal axis 6600, according to some embodiments. Insome embodiments, the outer edge of halo 5322 is arcuate, curved, etc.In some embodiments, halo 5322 extends along an entire perimeter ofdisplay device 5300. In some embodiments, the angled/curved profile ofhalo 5322 facilitates a directing of light. For example, in FIG. 66, anouter edge of halo 5322 is angled such that emitted light 6602 isgenerally directed towards a front of display device 5300.

Referring now to FIGS. 67 and 68, halo 5322 is shown in greater detail,according to some embodiments. FIG. 67 shows a front view of halo 5322,according to some embodiments. FIG. 68 shows a perspective view of halo5322, according to some embodiments. Halo 5322 is shown to include lightdirecting elements, shown as wave guides 6704, according to someembodiments. In some embodiments, wave guides 6704 are configured to atleast one of direct, diffuse, guide, etc., light emitted by one or moreof LEDs 6400. In some embodiments, wave guides 6704 are configured to atleast one of direct, diffuse, guide, etc., light emitted by acorresponding LED 6400. For example, wave guide 6704 is configured to atleast one of direct, guide, diffuse, etc., light emitted by LED 6400,according to some embodiments. In some embodiments, each of wave guides6704 include a corresponding LED 6400.

In some embodiments, wave guides 6704 are a substantially translucentand/or transparent material. In some embodiments, wave guides 6704 arecladded with an opaque material. In some embodiments, exterior surfacesof wave guide 6704 which do not either facilitate an entry or an egressof light into/out of wave guides 6704 is cladded with the opaquematerial. In some embodiments, the opaque material is painted ontoexterior surfaces of wave guides 6704.

In some embodiments, wave guides 6704 include a sweep portion 6808 and areceiving post 6806. In some embodiments, sweep portions 6808 of waveguides 6704 protrude from a rim 6702 (e.g., bezel, surrounding edge,etc.) of halo 5322. In some embodiments, wave guides 6704 protrude fromrim 6702 along a curved path. In some embodiments, a width of sweepportion 6808 of wave guides 6704 varies (e.g., decreases) along thecurved path. In some embodiments, wave guides 6704 include a receivingpost (e.g., a square receiving post, a rectangular receiving post, asquare receiving post, etc.) which protrudes from an end point of sweepportion 6808. In some embodiments, any or all of rim 6702, sweepportions 6808 and receiving posts 6806 are integrally formed.

In some embodiments, receiving posts 6806 are configured to facilitateentry of light into wave guides 6704. In some embodiments, receivingposts 6806 include a surface which is not covered with an opaquematerial (e.g., not cladded) configured to facilitate entry of lightemitted by one or more of LEDs 6400 into wave guide 6704. In someembodiments, receiving posts 6806 protrude such that an end of receivingposts 6806 is substantially adjacent to the corresponding LED 6400. Insome embodiments, the end of receiving posts 6806 contacts an exteriorsurface of a corresponding LED 6400.

Referring now to FIGS. 69 and 70, one of wave guides 6704 is shown ingreater detail, according to some embodiments. In some embodiments, waveguides 6704 are generally S-shaped. Wave guide 6704 includes sweepportion 6808 and receiving post 6806, according to some embodiments. Insome embodiments, sweep portion 6808 protrudes from rim 6702 of halo5322. Sweep portion 6808 is shown following path 6922 and havingthickness 6912, according to some embodiments. In some embodiments, path6922 is a centerline of sweep portion 6808. In some embodiments, path6922 is a curved path, having a non-constant radius. In someembodiments, path 6922 is generally S-shaped. In some embodiments, path6922 includes a convex portion 6924 and a concave portion 6926. In someembodiments, sweep portion 6808 protrudes from a first surface 6906 ofrim 6702. In some embodiments, sweep portion 6808 protrudes from asecond surface 6908 of rim 6702. In some embodiments, first surface 6902and second surface 6908 of rim 6702 are opposite each other and define athickness of rim 6702. In some embodiments, sweep portion 6808 protrudesfrom an interior surface 6928 of rim 6702. FIGS. 17 and 18 are shown toinclude a coordinate system 6900, according to some embodiments. In someembodiments, coordinate system includes an x-axis, a y-axis, and az-axis. Any of wave guides 6704 includes a corresponding coordinatesystem 6900, according to some embodiments. In some embodiments, waveguides 6704 are generally S-shaped and have non-constant width. In someembodiments, wave guides 6704 are generally S-shaped from a side view.In some embodiments, wave guides 6704 are generally S-shaped and have afirst end and a second end. In some embodiments, the second end isconfigured to receive light emitted by light emitting devices (e.g.,LEDs 6400).

In some embodiments, rim 6702 is coated with the opaque material. Insome embodiments, first surface 6906, second surface 6908 and interiorsurface 6928 are coated with the opaque material. In some embodiments,if sweep portion 6808 protrudes from interior surface 6928, at leastpart of an area of interior surface 6928 which sweep portion 6808protrudes from is configured to allow light to pass through. In someembodiments, exterior surface 6910 is configured to facilitate egress oflight from wave guide 6704. In some embodiments, exterior surface 6910is configured to diffuse light which passes through wave guide 6704along at least part of exterior surface 6910.

In some embodiments, sweep portion 6808 includes one or more exteriorsurfaces which are coated (e.g., cladded) with an opaque materialconfigured to restrict the exit of light from wave guide 6704. In someembodiments, sweep portion 6808 includes first surface 6902 and secondsurface 6904. In some embodiments, first surface 6902 and second surface6904 are opposite each other and are each offset an equal distance frompath 6922 in opposite directions. In some embodiments, first surface6902 and second surface 6904 substantially follow path 6922 at an offsetdistance. In some embodiments, first surface 6902 and second surface6904 are coated (e.g., cladded) with the opaque material.

In some embodiments, an axis 6810 extends tangent to a starting point6930 of path 6922. In some embodiments, an axis 6812 extends tangent toan end point of path 6922. In some embodiments, axis 6812 is a centralaxis of receiving post 6806. In some embodiments, axis 6812 extendstangent to the end point of path 6922 and is the central axis ofreceiving post 6806. In some embodiments, axis 6810 and axis 6812 aresubstantially parallel to each other. In some embodiments, axis 6810 andaxis 6812 are substantially parallel to each other and are offset adistance 7002 from each other. In some embodiments, distance 7002 is adistance which is perpendicular to both axis 6810 and axis 6812. In someembodiments, distance 6926 is parallel to the Z-axis of coordinatesystem 6900. In some embodiments, axis 6810 extends tangentiallyoutwards from starting point 6930 of path 6922 and starting point 6930of path 6922 is disposed at a center point of initial width 1632 ofsweep portion 6808. In some embodiments, axis 6810 and axis 6812 areoffset relative to each other along the X-axis of coordinate system 6900(e.g., laterally).

In some embodiments, sweep portion 6808 has a width 6914 and/or anopening 6918 for fasting to another component and/or enclosure piece.Width 6914 varies (e.g., decreases) along path 6922, according to someembodiments. In some embodiments, width 6914 decreases along path 6922until it is substantially equal to thickness 7006 of receiving post6806. In some embodiments, width 6914 decreases non-linearly. In someembodiments, sweep portion 6808 has initial width 1632 proximate theinterface (e.g., connection) between rim 6702 and sweep portion 6808. Insome embodiments, width 6914 decreases linearly. In some embodiments,width 6914 decreases (e.g., either linearly or non-linearly) along partof path 6922 and increases (e.g., either linearly or non-linearly) alonganother part of path 6922.

In some embodiments, receiving post 6806 protrudes from an end of sweepportion 6808. In some embodiments, receiving post 6806 protrudestangentially outwards from an endpoint of path 6922. In someembodiments, receiving post 6806 extends in a direction substantiallyparallel to the Y-axis. In some embodiments, receiving post 6806includes a receiving surface 1720, configured to facilitate entry oflight emitted by one of LEDs 6400. In some embodiments, all othersurfaces of receiving post 6806 are coated (e.g., cladded) with theopaque material to prevent light from exiting through the othersurfaces.

In some embodiments, sweep portion 6808 has a constant thickness 6912along an entire length of path 6922. In some embodiments, sweep portion6808 has a variable thickness 6912 with respect to path 6922. Forexample, in some embodiments thickness 6912 increases, decreases, or acombination of both, along path 6922. In some embodiments, thickness6912 is substantially equal to thickness 6906 of receiving post 6806. Insome embodiments, thickness 6912 changes (e.g., increases, decreases, ora combination of both) along path 6922 and is substantially equal tothickness 6906 of receiving post 6806 at an end of path 6922 whichreceiving post 6806 protrudes from.

In some embodiments, receiving post 6806 has a height 6916. In someembodiments, receiving post 6806 protrudes from the end of sweep portion6808 such that surface 6920 of receiving post is adjacent LED 6400. Insome embodiments, receiving post 6806 protrudes from the end of sweepportion 6808 such that surface 6920 is distance 7004 from LED 6400. Insome embodiments, distance 7004 is negligible.

Referring now to FIG. 71, a side view of LED board 6302 and halo 5322 isshown, according to some embodiments. In some embodiments, light emittedby LED 6400 is received by wave guide 6704 (e.g., through receiving post6806), travels through sweep portion 6808, and exits halo 5322 throughexterior surface 6910 of rim 6702. In some embodiments, light emitted byLED 6400 follows path 7102, generally. In some embodiments, path 7102 ispath 6922. In some embodiments, if exterior surfaces of wave guide 6704are coated (e.g., cladded) with an opaque material, light emitted by LED6400 travels through wave guide 6704 and reflects off the opaquematerial. In some embodiments, halo 5322 facilitates a glow of emittedlight along exterior surface 6910 of halo 5322. In some embodiments,halo 5322 diffuses light along sides 5308 of display device 5300. Insome embodiments, halo 5322 is manufactured from or includes (e.g., atexterior surface 6910) a light diffusing material. In some embodiments,halo 5322 is translucent. In some embodiments, halo 5322 is transparent.In some embodiments, halo 5322 acts as a lens and focuses light emittedby LED 6400 along sides 5308. In some embodiments, light emitted by LED6400 which enters wave guide 6704 is substantially bounded by exteriorsurfaces of wave guide 6704 and only enters wave guide 6704 throughreceiving post 6806 and only exits wave guide 6704 at rim 6702.

Halo 5322 facilitates a wider off-axis viewing angle of light emitted byLED 6400, according to some embodiments. In some embodiments, halo 5322facilitates notifying a user regarding information received by ordetermined by display device 5300. In some embodiments, halo 5322enables the notification to be visible by an observer generally facingany of sides 5308. In some embodiments, halo 5322 enables notificationsto an observer when the observer cannot view user interface 5306.

LED Controller

Referring now to FIG. 72, a controller 7000 is shown, according to someembodiments. In some embodiments, controller 7000 is or is included inLED board 6302. In some embodiments, controller 7000 is or is includedin controller 6002. In some embodiments, any of the functionality ofcontroller 7000 is included in any of controller 6002 and LED board6302. In some embodiments, controller 7000 is disposed within displaydevice 5300 and is communicably connected to at least one of controller6002 and LED board 6302. In some embodiments, controller 7000 ispositioned outside display device 5300 and is communicably connected toany controllers (e.g., controller 6002, LED board 6302, etc.) of displaydevice 5300.

Still referring to FIG. 72, controller 7000 is shown to includecommunications interfaces shown as input interface 7024, and outputinterface 7022. Interfaces 7024 and 7022 can include any number ofjacks, wire terminals, wire ports, wireless antennas, or othercommunications interfaces for communicating information and/or controlsignals. Interfaces 7024 and 7022 can be the same type of devices ordifferent types of devices. For example, input interface 7024 can beconfigured to receive an analog feedback signal (e.g., an outputvariable, a measured signal, a sensor output, a controlled variable)from sensor/equipment 7036 or a digital signal from controller 7034.Output interface 7022 can be a digital output (e.g., an optical digitalinterface) configured to provide a digital control signal (e.g., amanipulated variable, a control input) to user interface 7032 and/orLEDs 7026. In some embodiments, output interface 7022 is configured toprovide an analog output signal. In some embodiments, output interface7022 is configured to provide an analog output signal and a digitaloutput signal.

In some embodiments interfaces 7024 and 7022 can be joined as oneinterface rather than two separate interfaces. For example, outputinterface 7022 and input interface 7024 can be combined as one Ethernetinterface configured to receive network communications from controller7034 or a network. In some embodiments, controller 7034 provides both asetpoint and feedback via an Ethernet network. In some embodiments,output interface 7022 can be another standardized communicationsinterface for communicating data or control signals (e.g., analog ordigital). Interfaces 7022 and 7024 can include communicationselectronics (e.g., receivers, transmitters, transceivers, modulators,demodulators, filters, communications processors, communication logicmodules, buffers, decoders, encoders, encryptors, amplifiers, etc.)configured to provide or facilitate the communication of the signalsdescribed herein.

Still referring to FIG. 72, controller 7000 is shown to include aprocessing circuit 7002 having a processor 7204 and memory 7206.Processor 7204 can be a general purpose or specific purpose processor,an application specific integrated circuit (ASIC), one or more fieldprogrammable gate arrays (FPGAs), a group of processing components, orother suitable processing components. Processor 7204 is configured toexecute computer code or instructions stored in memory 7206 or receivedfrom other computer readable media (e.g., CDROM, network storage, aremote server, etc.).

Memory 7206 can include one or more devices (e.g., memory units, memorydevices, storage devices, etc.) for storing data and/or computer codefor completing and/or facilitating the various processes described inthe present disclosure. Memory 7206 can include random access memory(RAM), read-only memory (ROM), hard drive storage, temporary storage,non-volatile memory, flash memory, optical memory, or any other suitablememory for storing software objects and/or computer instructions. Memory542 can include database components, object code components, scriptcomponents, or any other type of information structure for supportingthe various activities and information structures described in thepresent disclosure. Memory 542 can be communicably connected toprocessor 540 via processing circuit 538 and can include computer codefor executing (e.g., by processor 540) one or more processes describedherein.

Referring still to FIG. 72, controller 7000 is shown receivinginformation from at least one of sensor/equipment 7036 and controller7034, according to some embodiments. In some embodiments, controller7000 receives information from sensor/equipment 7036 and determines anoperation of LEDs 7026 corresponding to the information received. Insome embodiments, LEDs 7026 are LEDs 6400. In some embodiments, LEDs7026 are LED board 6302. In some embodiments, controller 7000 isconfigured to determine an event (e.g., temperature exceeding athreshold value, emergency event, etc.) and is configured to adjust anoperation of LEDs 7026 for the event. In some embodiments, controller7000 receives information regarding an event from controller 7034 andadjusts an operation of at least one of user interface 7032 and LEDs7026 for the event. In some embodiments, sensor/equipment 7036 is any ofa temperature sensor, an air quality detector, building equipment, etc.,or any other sensor or equipment. In some embodiments, sensor/equipment7036 is more than one sensor and/or more than one equipment. Forexample, controller 7000 receives information from multiple temperaturesensors, according to some embodiments.

Controller 7000 is shown receiving information from sensor/equipment7036 through input interface 7024. In some embodiments, sensor/equipmentmodule 7010 receives the information from sensor/equipment 7036. In someembodiments, sensor/equipment module 7010 receives the information fromsensor/equipment 7036 and determines an event based on the receivedinformation. For example, in some embodiments, sensor/equipment module7010 periodically receives temperature information from a temperaturesensor and determines if the received temperature exceeds apredetermined threshold value. In another example, sensor/equipment 7036receives information from an indoor air quality sensor (e.g., a carbonmonoxide detector) and determines if the received indoor air qualityinformation is less than a predetermined threshold value. In someembodiments, controller 7000 receives information from any of one ormore controller, one or more equipment devices, one or more sensors, anetwork, etc., and determines an operation of user interface 7032 and/orLEDs 7026 based on the received information. Controller 7000 may receiveinformation through a wired connection at input interface 7024, awireless connection at input interface 7024, or a combination of both.

In some embodiments, sensor/equipment module 7010 determines an eventbased on the received information and provides the event to LED module7008. For example, if sensor/equipment module 7010 determines that theindoor air quality has dropped below a predetermined value,sensor/equipment module 7010 provides the determined event to LED module7008. In some embodiments, sensor/equipment module 7010 provides theinformation received from sensor/equipment 7036 to user interface module7020. For example, in some embodiments, if sensor/equipment module 7010receives temperature information from sensor/equipment 7036,sensor/equipment module 7010 provides the temperature information touser interface module 7020. In some embodiments, user interface module7020 is configured to determine control signals for user interface 7032to display the information received from sensor/equipment module 7010 toa user. In some embodiments, sensor/equipment module 7010 is configuredto provide LED module 7008 with at least one of information receivedthrough input interface (from at least one of controller 7034 andsensor/equipment 7036) and the determined or received event.

In some embodiments, user interface module 7020 is configured todetermine control signals for user interface 7024. In some embodiments,user interface 7032 is user interface 5306. In some embodiments, userinterface module 7020 is configured to determine control signals foruser interface 7032 to display messages, information, graphicalrepresentations of information, data, etc. In some embodiments, userinterface module 7020 also receives information from user interface 7032through input interface 7024. In some embodiments, user interface module7020 receives commands, directives, requests, etc., from user interface7032 and adjusts an operation (e.g., a displayed message) of userinterface 7032 based on the command, request, etc., received from userinterface 7032. In some embodiments, user interface module 7020 receivesa request from user interface 7032 to display certain data, and userinterface module 7020 adjusts an operation of user interface 7032 todisplay the requested data.

In some embodiments, controller 7000 receives any of information and anevent from controller 7034. For example, in some embodiments, controller7034 is communicably connected with sensor/equipment 7036 and isconfigured to analyze, process, group, etc., information formsensor/equipment 7036 and determine if an event has occurred. In someembodiments, controller 7034 provides the information and/or event datato at least one of user interface module 7020 and LED module 7008.

Referring still to FIG. 72, memory 7206 is shown to include LED module7008, according to some embodiments. In some embodiments, LED module7008 is configured to determine an operation of one or more LEDs (e.g.,LEDs 7026, LEDs 6400) based on information received from any ofsensor/equipment module 7010, user interface module 7020, user interface7032, controller 7034, and sensor/equipment 7036. LED module 7008determines any of a color, a pattern, an intensity, etc., of the one ormore LEDs based on the received information and determines signals toadjust an operation of one or more LEDs based on the receivedinformation.

LED module 7008 is shown to include an LED database 7012, a color module7014, a pattern module 7016, and an intensity module 7018. In someembodiments, LED database 7012 stores information regarding a patternedoperation of one or more LEDs based on a received event and/or receivedinformation. For example, if LED module 7008 receives an event fromsensor/equipment module 7010, controller 7034, sensor/equipment 7036,etc., indicating that the indoor air quality has dropped below apredetermined value, LED module 7008 may retrieve a set of instructionsfrom LED database 7012 regarding an operation of LEDs based on theevent. In some embodiments, LED database 7012 includes informationregarding an operation of LEDs for a variety of events, including butnot limited to, an increased temperature event, a decreased temperatureevent, a low indoor air quality event, an emergency event, a firedetection event, an equipment failure event, a calendar date event, atime of day, etc. In some embodiments, LED database 7012 includes a setof predetermined instructions regarding an operation of LEDs for each ofthese events.

In some embodiments, LED database 7012 includes a set of predeterminedinstructions for each of a set of predefined events. In someembodiments, LED database 7012 can be updated and/or customized. Forexample, in some embodiments, LED database 7012 can receive directivesfrom user interface 7032 to change an operation of one or more of theLEDs (e.g., color, on-off pattern, intensity, timing, etc.) to modifythe predetermined instructions for one or more of the predefined events.In some embodiments, additional events can be added to LED database 7012along with corresponding LED operation instructions for the additionalevents. In some embodiments, for example, controller 7000 includes awireless radio (e.g., a Bluetooth wireless radio) configured tointerface with a user device (e.g., a smartphone). The LED database 7012is configured to be updated or modified based on directives receivedfrom the user device. For example, if a user wants to benotified/reminded of an event on a certain date at a specific time, theuser may add an event to LED database 7012 to adjust an operation of oneor more LEDs according to a predetermined pattern, set of rules, etc.,on the certain date at the specific time.

In some embodiments, upon receiving an event and/or information, LEDdatabase 7012 provides the instructions to color module 2014, patternmodule 7016, and intensity module 7018. For example, if LED database7012 receives a night-time event (e.g., from a clock or from a lightdetector), LED database 7012 may retrieve a specific set of instructions(e.g., dim all LEDs by 50%, turn off several LEDs, adjust a color of oneor more LEDs to blue, etc.) for the LEDs (e.g., LEDs 7026, LEDs 6400,etc.) corresponding to the night-time event.

In some embodiments, LED database 7012 includes instructions for variousevents to adjust a color of one or more of the LEDs (e.g., red, blue,green, etc.), adjust an intensity of one or more of the LEDs, turn oneor more of the LEDs on or off, patterningly adjust a color of one ormore of the LEDs, patterningly adjust an intensity of one or more of theLEDs, patterningly turn one or more of the LEDs on or off, etc. In someembodiments, any of the color, intensity, on/off state, etc., of the oneor more LEDs is patterned over time (e.g., all LEDs are turned on for 5seconds, then turned off for 5 seconds, and this is repeated), orpatterned based on a predetermined position of the one or more LEDs(e.g., turn a first LED on, then turn a second LED on, then turn a thirdLED on and turn the first LED off, then turn a fourth LED on and turnthe second LED off, then turn a fifth LED on and turn the third LED off,etc.), or patterned based on both time and position of the one or moreLEDs.

In some embodiments, one or more of the set of instructions stored inLED database 7012 extend for a time duration, and are repeated. Forexample, some of the sets of instructions may last for five seconds(e.g., a patterned operation of the LEDs for five seconds) and berepeated a predetermined number of times, while other sets ofinstruction may last only two seconds (e.g., increase intensity from 0%to 5300% for all LEDs over a 1 second time duration, then decreaseintensity from 5300% to 0% for all LEDs over a 1 second time duration),and repeated.

In some embodiments, sets of instructions are combined. For example, insome embodiments, all events which indicate an increase in temperatureinclude a same patterned intensity operation of LEDs (e.g., linearlyincrease intensity of all LEDs from 0% to 5300% over a five second timewindow). However, within the set of all events which indicate anincrease in temperature, other operations of the LEDs (e.g., color) mayvary based on other factors (e.g., which temperature from a set oftemperatures is increasing, how fast the temperature increases, etc.).

Any of the color, pattern, intensity, etc., of the one or more LEDs maybe adjusted over a time window linearly (e.g., increase intensity from0% to 5300% linearly over a 5 second time window) or may be adjustedover a time window non-linearly (e.g., increase intensity from 0% to5300% according to an exponential function, a polynomial, etc.).

In some embodiments, the instructions stored in LED database 7012 dependon the particular types of LEDs used. For example, some LEDs may not bemulti-color LEDs and may only actuate between an on state and an offstate, according to some embodiments. In some embodiments, LED database7012 stores a map of positions of the LEDs and abilities of each of theLEDs (e.g., dimming abilities, maximum light intensity, etc.).

In some embodiments, controller 7000 does not include LED database 2012,and receives instructions from any of controller 7034 and/or a networkto adjust an operation of any of a color, a pattern, an intensity (e.g.,dimming), etc., of any of the LEDs.

Referring still to FIG. 72, LED module 7008 is shown including colormodule 2014, pattern module 7016 and intensity module 7018. In someembodiments, color module 2014, pattern module 2016, and intensitymodule 7018 are configured to determine any of voltage, current, digitalsignals, analog signals, etc., to adjust an operation of one or moreLEDs according to the determined operation received from any of LEDdatabase 7012, controller 7034, etc. LED module 7008 may include anypredefined script objects, functions, or electrical components (e.g.,resistors, capacitors, inductors, transformers, etc.) necessary todetermine voltage, current, etc., required to operate the LEDs toproduce the desired operation. In some embodiments, LED module 7008 usesPulse Width Modulation and adjusts a duty cycle to change a brightnessof one or more of the LEDs.

In some embodiments, LED module 7008 is connected to one or more LEDs(e.g., LEDs 7026, LEDs 6400, etc.). In some embodiments, LED module 7008adjusts an operation of the one or more LEDs to produce the desiredeffect (e.g., dimming, changing color, patterned dimming, patternedchange in color, etc.). In some embodiments, the one or more LEDs eachcorrespond to one or more wave guide 6704 to any of diffuse, direct,scatter, focus, etc., light emitted by the one or more LEDs along sides5308 of display device 5300.

Thermostat with Halo Light System and Emergency Features

Referring now generally to FIGS. 73-77, the control device 214 is shownand described with a halo LED interface system for providing a user withemergency indications and/or directions, according to various exemplaryembodiments. The control device 214 as described with reference to FIGS.73-77 can include some and/or all of the operations as described withFIGS. 2-39 and can interface with, receive data from, and/or control anyof the systems and/or devices as described with reference to FIGS. 2-39.More particularly, the emergency and direction based features asdescribed with reference to FIGS. 2-39 can be implemented in the controldevice 214 and used to operate the halo LED interface. Similarly, thecontrol device 214 can include some and/or all of the operations asdescribed with FIGS. 40-52 and can interface with, receive data from,and/or control any of the systems and/or devices as described withreference to FIGS. 40-52. More particularly, the emergency and directionbased features as described with reference to FIGS. 40-52 can beimplemented in the control device 214 and used to operate the halo LEDinterface.

The halo LED interface as described in FIGS. 73-77 can be the same asand/or similar to the halo system as described with reference to FIGS.53-72. Specifically, the mechanical structural components, LEDs, and/orprocessing logic as described with reference to FIGS. 73-77 can beimpalement in the control device 214 to allow the control device 214 toprovide emergency indications, directions, emergency directions, and/orcommunicate any other kind of information to a user via the halointerface. Furthermore, halo systems and devices are further describedin U.S. patent application Ser. No. 14/104,669 filed Dec. 12, 2013 (nowU.S. Pat. No. 9,824,549), the entirety of which is incorporated byreference herein. In some embodiments, the display device 5300 asdescribed with reference to FIGS. 53-72 includes some and/or all of thecomponents and/or is configured to perform some and/or all of theoperations of the of any of the thermostats, user devices, displaydevices, etc., specifically, the components and/or the operations of thecontrol device 214 as described with reference to FIGS. 73-77.

Referring now to FIG. 73, control device 214 is shown including a halo7300 for providing directions to a user, according to an exemplaryembodiment. Halo 7300 can be configured to diffuse light generated byone or multiple LEDs. Halo 7300 can be the same and/or similar to thehalo 5322 as described with reference to FIGS. 53-72. Control device 214can include any of the mechanical and/or electronic components describedwith reference to FIGS. 53-72 to operate the halo 7300 (e.g., the LEDboard 6302, the LEDs 6400, the wave guides 6704, etc.). In FIG. 73, thehalo 7300 is shown to surround a base portion 7308 of the control device214. The base portion can be configured to be mounted to a wall tocouple the control device 214 to a wall or other surface.

The control device 214 includes a user interface 7302 in someembodiments. The user interface 7302 may be a transparent touch screeninterface displaying information configured to display information to auser and receive input from the user. The user interface 7302 may be thesame as, similar to, and/or a combination of touch-sensitive panel 704,the electronic display 706, and/or the ambient lighting 708 as describedwith reference to FIG. 7 and/or the user interface 5306 as describedwith reference to FIG. 53.

The user interface 7302 may be transparent such that a user can viewinformation on the display and view the surface located behind thedisplay. Thermostats with transparent and cantilevered displays aredescribed in further detail in U.S. patent application Ser. No.15/146,649 filed May 4, 2016, the entirety of which is incorporated byreference herein.

The user interface 7302 can be a touchscreen or other type of electronicdisplay configured to present information to a user in a visual format(e.g., as text, graphics, etc.) and receive input from a user (e.g., viaa touch-sensitive panel). For example, the user interface 7302 mayinclude a touch-sensitive panel layered on top of an electronic visualdisplay. A user can provide inputs through simple or multi-touchgestures by touching the user interface 7302 with one or more fingersand/or with a stylus or pen. The user interface 7302 can use any of avariety of touch-sensing technologies to receive user inputs, such ascapacitive sensing (e.g., surface capacitance, projected capacitance,mutual capacitance, self-capacitance, etc.), resistive sensing, surfaceacoustic wave, infrared grid, infrared acrylic projection, opticalimaging, dispersive signal technology, acoustic pulse recognition, orother touch-sensitive technologies known in the art. Many of thesetechnologies allow for multi-touch responsiveness of user interface 7302allowing registration of touch in two or even more locations at once.The display may use any of a variety of display technologies such aslight emitting diode (LED), organic light-emitting diode (OLED),liquid-crystal display (LCD), organic light-emitting transistor (OLET),surface-conduction electron-emitter display (SED), field emissiondisplay (FED), digital light processing (DLP), liquid crystal on silicon(LCoC), or any other display technologies known in the art. In someembodiments, the user interface 7302 is configured to present visualmedia (e.g., text, graphics, etc.) without requiring a backlight.

The user interface 7302 is configured to display an arrow 7304 in someembodiments. The arrow 7304 can aid a user in navigating a building. Forexample, the arrow 7304 can be a direction (e.g., emergency direction,navigation direction, etc.) as described with reference to FIGS. 40-52.The arrow 7304 can aid a user in navigating a building to find aparticular conference room, office, etc. Furthermore, the arrow 7304 canbe an emergency response direction. For example, the arrow 7304 can aida user to navigate out of a building in an active shooter situation,navigate to a safe zone within a building, etc. The arrow 7304 can be aparticular color, e.g., black, red, yellow, green, etc. In someembodiments, where the user interface 7302 is transparent, the arrow7304 can include a border 7306 to help the arrow 7304 be distinguishablefrom a wall which may have a similar color as the arrow 7304.

For example, an emergency evacuation arrow may be colored red. However,if the control device 214 is installed on a red colored wall, the arrow7304 may be difficult to see for a user. In this regard, the controldevice 214 can be configured to cause the user interface 6902 to displaythe arrow 7304 with the border 7306. The border 7306 may be black, red,yellow, orange, green, blue etc. and/or any other color which helps thearrow 7304 stand out and be visible to a user. In some embodiments, auser programs, via the user interface 7302, a wall color and/or a bordercolor 7304 in order for the control device 214 to appropriately generatethe arrow 7304. In some embodiments, the control device 214 includescolor sensors configured to determine a color of a wall that the controldevice 214 is installed in an automatically select the color for theborder 7306 and generate the arrow 7304 with the selected border color.For example, if the wall which the control device 214 is located by isred, the arrow 7304 may be generated to be a red color with a bluecolored border 7306 to help the arrow 7304 stand out to a user.

In addition to, or in place of, the navigation direction (e.g., thearrow 7304) displayed by the control device 214 on the user interface7302, the user device can operate the halo 7300 to cause the controldevice 214 to communicate navigation directions and/or indications to auser. In some embodiments, in the event of an emergency, the halo, inpart and/or in its entirety (e.g., one, multiple, or all of the LEDSlighting the halo 7300) can turn on causing the control device 214 tohave an ambient halo light (e.g., a red light for an emergency). In someembodiments, the halo 7300 is operated by the control device 214 tocommunicate a navigation and/or emergency response direction to a user.

For example, if a user needs to make a right turn, the halo 7300 mayoperate such that the right side of the halo 7300 (e.g., as shown inFIG. 73) is illuminated. In some embodiments, the halo 7300 is activatedin a pattern. For example, to communicate to a user to make a rightturn, the halo 7300 can activate from left to right (e.g., turn on for apredefined period of time to cause a trail of light to move from left toright). In some embodiments, the pattern moves across the halo 7300 fromleft to right while in some embodiments, the halo LEDs of the halo 7300are activated and held on one at a time from left to right until all theLEDS are activated. In some embodiments, the direction displayed on theuser interface 7302 and the direction communicated by the halo 7300 arerelated, i.e., if the user should make a left turn, both the userinterface 7302 and the halo 7300 communicate the left turn indication tothe user.

Referring now to FIG. 74, the control device 214 is shown including ahalo 7400 surrounding, in part, the user interface 7302. While the halo7400 is shown to surround the user interface 7302 and not the baseportion 7304, in some embodiments, the control device 214 includes boththe halo 7300 and the halo 7400, i.e., the control device 214 includes asingle halo (or multiple halos) surrounding, in whole or in part, thecontrol device 214. The halo 7400 can be the same as and/or similar tothe halo 7300 as described with reference to FIG. 73.

The control device 214 is configured to cause the user interface 7302 todisplay a map 7402, in some embodiments. The map 7402 may be multipleemergency response directions, e.g., directions helping a user navigatethrough and/or out of a building in the event of an emergency (e.g., anactive shooter situation, a fire, etc.). The map 7402 can indicate thecurrent location of a user, an indication of the control device 214 onthe map, and a navigation path including one or multiple turns toevacuate a building. In some embodiments, the control device 214 causesthe halo 7400 to operate to display a complementary indication to auser. For example, if the next turn on the map 7402 is a right turn, thehalo 7400 can be operated to communicate a right turn to the user.

For example, the control device 214 is configured to cause LEDsilluminating the halo 7400 to operate in a pattern, e.g., a sweepingpattern from left to right. In some embodiments, rather than a sweepfrom left to right, the LEDs can be activated and held on one at a timeat predefined intervals from left to right. In some embodiments, aparticular set of LEDs can be operated as a blinker. For example, LEDson a left side of the halo 7400 can be operated in a blinking mode toindicate a left turn while LEDs on the right side of the halo 7400 canbe operated in a blinking mode to indicate a right turn.

Although the control device 214 described with reference to FIGS. 73-74uses the halos 7300 and/or 7400 to communicate the existence of anemergency and/or emergency response directions, the control device 214can operate a halo LED system to cause the halos 7300 and/or 7400 todisplay non-emergency information. For example, if the control device214 determines that there is a condition that requires user input, thecontrol device 214 can activate LEDs of a halo LED system (e.g., turnthe LEDs on constantly, blink the LEDs at a particular frequency, causethe LEDs to emit light of a particular color, etc.) to indicate to theuser that they should approach the control device 214 and provide inputto the control device 214 via the user interface 7302.

In some embodiments, the control device 214 is located in a hotel room.When a user first enters the hotel room, the control device 214 maydetect the presence of the user and activate the halo LEDs, illuminatingthe halos 7300 and/or 7400 to indicate that the user should approach thecontrol device 214 to provide the control device 214 input. The controldevice 214 can present information e.g., check-in and check-outinformation, facilitate a booking payment, request a wakeup time (andsound an alarm once the wakeup time occurs), prompt a user for preferredenvironmental settings (e.g., temperature setpoint), etc.

The control device 214 can activate halo LEDs to illuminate the halos7300 and/or 7400 to provide alarm functionality. For example, a user mayset an alarm time and/or date on the control device 214 via the userinterface 7302. The control device 214 is configured to sound an alarmwhen the alarm time and/or date occurs. The alarm may be an audio basedalarm sounded via the speakers 710. Furthermore, the control device 214can activate the halo LEDs to illuminate the halos 7300 and/or 7400 toawaken the user. The LEDs can be pulsed on and off at particularfrequencies and/or ramp a light intensity of the LEDs up and/or down.

Furthermore, the control device 214 can be configured to integrate, viathe network 602, with a television. The television may be a smarttelevision configured to receive control input via the network 602. Forexample, the television may be connected to the Internet. An Internetserver may store settings for the television and push settings to thetelevision causing the television to implement the settings. Examples ofsettings may be volume, television channel, powering on or off (e.g.,going from a low power state to a fully operational power state), etc.

In some embodiments, the control device 214 receives, via the microphone726 audio commands (e.g., to turn volume up or down, change a channel upor down, pause a video being played on the television, play the video,fast forward the video, rewind the video, etc.). The control device 214can process the audio data recorded, determine the command, and push thecommand to the Internet television server which can in turn cause thetelevision to implement the command. In some embodiments, whenever thecontrol device 214 is processing audio data and/or causing thetelevision to implement a command based on the processed audio data, thecontrol device 214 can operate LEDs of the halos 7300 and/or 7400. Forexample, when the control device 214 is listening to a user, the LEDsmay be operated in a first pattern or in a first color. When the controldevice 214 is processing the audio data, the control device 214 canoperate the LEDs in a second pattern and/or at a second color.

Referring now to FIG. 75, the control device 214 is shown in greaterdetail to include the processing circuit 734, the processor 740, and thememory 742 as describe with reference to FIG. 7. Furthermore, thecontrol device 214 is shown to include the communications interface 732as described with reference to FIG. 7. The processing circuit 734 isconfigured to receive emergency and/or non-emergency information fromthe communications interface 732 via a network 602 and is configured tooperate the user interface 7302 and/or a halo light emitting diode (LED)system 7508 which is included by the control device 214. The processingcircuit 734 is configured to operate the halo LED system 7508 and theuser interface 7302, in some embodiments, to communicate messages (e.g.,emergency response directions), to a user in response to a particularevent occurring (e.g., an emergency situation e.g., a fire, a flood, ahurricane, a tornado, an active shooter, etc.).

The halo LED system 7508 can be the same as and/or similar to thecomponents of FIGS. 53-72 and can be configured to cause light to bediffused through a halo (e.g., the halo 7300 and/or the halo 7400). Thehalo LED system 7508 can include one or multiple LEDs (e.g., singlecolor LEDS, multi-color LEDS, etc.) which may be the same as and/orsimilar to the LEDs 6304, the halo LEDs 7026, and/or the LEDs 6400 asdescribed with reference to FIGS. 53-72. The halo LED system 7508 caninclude an LED board, e.g., the LED board 6302, wave guide, e.g., thewave guides 6704, and/or any other mechanical, computing, or logiccomponent configured to operate the halo LED system 7508.

The control device 214 is shown to receive both emergency andnon-emergency data from one or multiple data streams via the network602. The emergency and non-emergency data can be received from thebuilding management system 610, the building emergency sensors 606,and/or the weather server 608 as described with reference to FIG. 6 andelsewhere herein. Furthermore, the control device 214 is configured toreceive the emergency and/or non-emergency information from the socialmedia servers 4011 as described with reference to FIG. 40 and elsewhereherein. In some embodiments, the emergency data indicates one or moreemergency conditions, e.g., a hurricane, an active shooter, a fire, etc.and can be measured, sensed, recorded, and/or generated by the buildingmanagement system 610, the building emergency sensors 606, the weatherserver 608, and/or the social media servers 4011. For example, if a userposts on a social media platform operated by the social media servers4011 that there is an active shooter in the building, the emergency datastream may indicate that there is an active shooter and may be receivedfrom the social media servers 4011. Similarly, the weather server 608can provide an indication of a storm warner, a blizzard, etc.

The memory 742 is shown to include an emergency identifier 7500. Theemergency identifier 7500 is configured, in some embodiments, to analyzedata streams receive from the network 602 to determine whether the dataof one or more of the data streams indicates an emergency. For example,in some embodiments, the data of a particular data stream may beindicative of an emergency occurring, a type of emergency occurring,etc. In some embodiments, the data received via the network 602 islabeled as an emergency and the emergency identifier 7500 can identifythat data as representing an emergency by identifying whether the labelis present. In some embodiments, the emergency identifier 7500 itselfanalyzes values within the data to determine whether an emergency ispresent.

For example, if the data received from the network 602 is indicative ofa particular ambient temperature, the emergency identifier 7500 canidentify whether the particular temperature is indicative of adangerously cold temperature (e.g., by comparing the temperature to athreshold value, e.g., by determining whether the temperature is lessthan the threshold value). Similarly, the emergency identifier 7500 isconfigured, in some embodiments, to determine whether wind speed datareceive from the weather server 608 indicates hurricane level winds(e.g., wind speed above a predefined amount).

The memory 742 includes display information controller 7502. The displayinformation controller 7502 is configured to generate information forthe halo controller 7504 and/or the user interface controller 7506 todisplay. For example, in some embodiments, the information may beindicative of the emergency and/or non-emergency data receive from thenetwork 602. For example, in some embodiments, if an outdoor ambienttemperature is received from the network 602, the display informationcontroller 7502 can communicate a value of the outdoor ambienttemperature to the halo controller 7504 and/or the user interfacecontroller 7506. The user interface controller 7506 can cause the userinterface 7302 to display a numeric value (or other interface element)representing the ambient temperature. The halo controller 7504 isconfigured to cause the halo LED system 7508 to display an indication ofthe current temperature (e.g., illuminate in a particular color and/orwith a particular temperature that is based on (e.g., is a function of)the temperature value. For example, the colors displayed by the halo LEDsystem 7508 may be blue and red. The color displayed by the halo LEDsystem 7508 may scale from blue to red as the temperature increases.

The display information controller 7502 is configured, in someembodiments, to generate emergency response directions and cause thehalo controller 7504 and/or the user interface controller 7506 tocommunicate the emergency response directions to a user. In someembodiments, the display information controller 7502 includes someand/or all of the operations of the display device 4300 for generatingand displaying directions as described with reference to FIGS. 40-52. Insome embodiments, the display information controller 7502 includes someand/or all of the operations of the emergency module 756, the occupancymodule 754, the healthcare module 752, the hotel module 750, and/or anyother module as described with reference to FIG. 7 and elsewhere herein.

In some embodiments, the emergency response directions are one ormultiple instructions to navigate a building (e.g., evacuate abuilding), respond to an active shooter (e.g., fortify a room, turnlights off, hide under a desk, etc.), respond to a hurricane or tornado(e.g., close windows, close shutters, move away from windows, hide underdesks or tables, etc.). The display information controller 7502 isconfigured to communicate the emergency response directions to the halocontroller 7504 and/or the user interface controller 7506.

Furthermore, the display information controller 7502 is configured, insome embodiments, to override the current operate (e.g., display) of thehalo LED system 7508 and/or the user interface 7302. For example, if thehalo LED system 7508 and the user interface 7302 are currentlydisplaying non-emergency information (e.g., information pertaining tonormal weather, non-emergency building events, etc.) the displayinformation controller 7502 can cause the halo controller 7504 and/orthe user interface controller 7506 to override the display ofinformation by the halo LED system 7508 and/or the user interface 7302with the emergency response directions.

In some embodiments, in response to receiving emergency responsedirections, the halo controller 7504 can override a current operation ofthe halo LED system 7508. For example, the halo LED system 7508 mayslowly blink (or linearly, exponentially, etc. vary intensity) at aparticular color (e.g., green, blue, etc.) and/or turn on constantly atthe particular color to indicate that a user has a message,notification, or otherwise that the control device 214 requires theirinput. However, if the display information controller 7502 providesemergency response directions to the halo controller 7504. The halocontroller 7504 can override the operation of the halo LED system 7508with the emergency response directions and/or an indication of anemergency. For example, the halo controller 7504 can cause the color ofthe LED system 7508 to change color to another color indicative of anemergency (e.g., red, orange, etc.) and/or change from being constantlyon (or off) to blinking at a particular frequency (e.g., every halfsecond) to gain the attention of a user.

The user interface controller 7506 can be configured to cause the userinterface 7302 to display the emergency response directions and/or canbe configured to override any other information displayed on the userinterface 7302 in response to receiving an indication of an emergencyfrom the display information controller 7502. For example, the userinterface 7302 could display navigation instructions for a user tonavigate to a particular conference room. The navigation instructionsand/or request for the instructions can be receive via the network 602via a data stream. However, in response to determining that there is aweather emergency (e.g., tornado, flooding, earthquake, etc.) the userinterface controller 7506 can override the display of the normalnon-emergency y building navigation directions and cause the userinterface 7302 to display emergency response directions (e.g., anavigation arrow for evacuation, shooter response directions, etc.).

Referring now to FIG. 76, a process 7600 is shown for operating the haloLED system 7508 and/or the user interface 7302 to display emergencyresponse directions, according to an exemplary embodiment. The controldevice 214 is configured to perform the process 7600 in someembodiments. Furthermore, any computing device, e.g., the display device4002, the user device 4012, the display device 5300 can include someand/or all of the components required to perform the process 7600 andcan be configured to perform the process 7600.

In step 7602, the control device 214 receives building information fromone or more data sources. The data sources can be weather related datasources indicating weather conditions of cities, towns, states,countries, etc. and can be received from the weather server 608 via thenetwork 602. In some embodiments, the data is social media data, e.g.,trending posts, videos, etc. receive from the social media servers 4011via the network 602. Furthermore, the data can be indications of indoortemperatures, indoor air quality values (e.g., carbon monoxide), etc.receive from the building emergency sensors 606.

In step 7604, the control device 214 can determine whether the buildinginformation receive in the step 7602 is indicative of an emergency. Forexample, in some embodiments, the data received in the step 7602 istagged as an emergency and/or a particular type of emergency. Forexample, weather data received via a weather data stream from theweather server 608 can indicate that a hurricane is present.Furthermore, an emergency pull handle (e.g., a building emergency sensor606) can be triggered causing an indication of a fire or active shooterwithin a building to the control device 214.

In step 7606, in response to determining that a building emergency isoccurring as determined in the step 7604, the control device 214 isconfigured to generate one or more emergency response directions. Forexample, the control device 214 can generate one or more directions forresponding to an emergency, e.g., directions for navigating a building,directions for responding to an active shooter, a fire, etc. In step7608, the control device 214 can display the emergency directions on theuser interface 7302. In some embodiments, the directions are text basedinstructions “Close Windows,” “Hide Under Desk”, or are visualindications, e.g., arrows, maps, etc.

In step 7610, the control device 214 cause the halo LED system 7508 tooperate to provide an indication of the emergency determine din the step7604 to a user and/or provide an indication of the emergency responsedirections to a user. For example, the control device 214 could causethe halo LED system 7508 to illuminate (e.g., turn on constantly, blinkat a particular frequency, etc.) a particular color (e.g., red) toindicate that there is an emergency. In various embodiments, the haloLED system 7508 operates LEDs of the halo LED system 7508 to provideemergency navigation directions. For example, the halo LED system 7508could be operated that LEDs on a left side of the control device 214blink to indicate to make a left turn down a hallway. Furthermore, thelights could turn on in a pattern from left to right to indicate theleft turn.

Referring now to FIG. 77, a process 7700 is shown for displayingnon-emergency information on the user interface 7302 and/or the halo LEDsystem 7508 and overriding the display of non-emergency information withemergency information in response to receiving an emergency from a datastream, according to an exemplary embodiment. The control device 214 isconfigured to perform the process 7700 in some embodiments. Furthermore,any computing device, e.g., the display device 4002, the display device5300, the user device 4012 can include some and/or all of the componentsrequired to perform the process 7700 and can be configured to performthe process 7700.

In step 7702, the control device 214 can receive non-emergency data froma first data stream from at least one of the network or a sensor. Thecontrol device 214 can receive the non-emergency data from the network602, e.g., from the building management system 610, from the buildingemergency sensor 606, from the weather server 608, and/or from thesocial media servers 4011. Furthermore, the non-emergency data can bereceived from a sensor of the control device 214 (e.g., a temperaturesensor, a pressure sensor, a humidity sensor, etc.). In step 7704, basedon the non-emergency data, the control device 214 can cause the userinterface 7302 to display non-emergency information.

For example, the user interface 7302 could display temperatures,humilities, weather reports, social media events, scheduled buildingevents, building notifications, news stories, etc. In step 7706, thecontrol device 214 operates the halo LED system 7508 to display anindication of the non-emergency data. For example, if the data is new,the halo LED system 7508 may illuminate to notify a user that newinformation is received. If the non-emergency data indicates ambientoutdoor temperature, the color of the halo LED system 7508 mayilluminate to a color that is a function of the temperature (e.g.,between blue and red to indicate hot or cold.)

In step 7708, the control device 214 receives emergency data from asecond data stream from at least one of the network and the sensor. Theemergency data can be received from a second data stream and/or from thefirst data stream and can be used to override the display of informationbased on the non-emergency information. For example, the non-emergencyinformation could be received from the building management system 610via a data stream of the building management system 610 however based onreceiving emergency data from a data stream of the weather server 608,the control device 214 can override display of the information on theuser interface 7302 and/or the halo LED system 7508.

In step 7710, the control device 214 can determine whether the emergencydata receive din the step 7708 is indicative of an emergency. Forexample, the data received from the second data stream may be labeled asemergency and non-emergency data and the control device 214 can identifywhether the data of the second data stream is the emergency data basedon the label. In some embodiments, the control device 214 itselfidentifies whether the data of the second data stream is emergency data,e.g., determine whether a wind speed is greater than a predefinedamount, determine whether an outdoor temperature is lower than apredefined amount, determine whether a snowfall amount is greater than apredefined amount, etc.

In step 7712, the control device 214 determines emergency response basedon the emergency data. For example, if the emergency data indicates thatthere is a tornado, the control device 214 can generate route directionsfor navigating to a tornado shelter or safe area of a building.Furthermore, if there is an active shooter in the building, the controldevice 214 can generate emergency response directions which providenavigation to an area where the shooter is not present.

In step 7714, the control device 214 can override the display of thenon-emergency information on the user interface 7302. For example, thecontrol device 214 can cause the user interface 7302 to stop displayingthe non-emergency information and begin displaying the emergencyresponse directions. Similarly, the control device 214, in step 7716,can override the operation of the halo LED system 7508 to display theemergency response directions. The step of overriding and displaying theemergency response directions on the user interface 7302 and/or the haloLED system 7508 can be the same and/or similar to the steps 7608 and/or7610 as described with reference to FIG. 76.

Configuration of Exemplary Embodiments

The construction and arrangement of the systems and methods as shown inthe various exemplary embodiments are illustrative only. Although only afew embodiments have been described in detail in this disclosure, manymodifications are possible (e.g., variations in sizes, dimensions,structures, shapes and proportions of the various elements, values ofparameters, mounting arrangements, use of materials, colors,orientations, etc.). For example, the position of elements may bereversed or otherwise varied and the nature or number of discreteelements or positions may be altered or varied. Accordingly, all suchmodifications are intended to be included within the scope of thepresent disclosure. The order or sequence of any process or method stepsmay be varied or re-sequenced according to alternative embodiments.Other substitutions, modifications, changes, and omissions may be madein the design, operating conditions and arrangement of the exemplaryembodiments without departing from the scope of the present disclosure.

The present disclosure contemplates methods, systems and programproducts on any machine-readable media for accomplishing variousoperations. The embodiments of the present disclosure may be implementedusing existing computer processors, or by a special purpose computerprocessor for an appropriate system, incorporated for this or anotherpurpose, or by a hardwired system. Embodiments within the scope of thepresent disclosure include program products comprising machine-readablemedia for carrying or having machine-executable instructions or datastructures stored thereon. Such machine-readable media can be anyavailable media that can be accessed by a general purpose or specialpurpose computer or other machine with a processor. By way of example,such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROMor other optical disk storage, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to carry or storedesired program code in the form of machine-executable instructions ordata structures and which can be accessed by a general purpose orspecial purpose computer or other machine with a processor. Combinationsof the above are also included within the scope of machine-readablemedia. Machine-executable instructions include, for example,instructions and data which cause a general purpose computer, specialpurpose computer, or special purpose processing machines to perform acertain function or group of functions.

Although the figures show a specific order of method steps, the order ofthe steps may differ from what is depicted. Also two or more steps maybe performed concurrently or with partial concurrence. Such variationwill depend on the software and hardware systems chosen and on designerchoice. All such variations are within the scope of the disclosure.Likewise, software implementations could be accomplished with standardprogramming techniques with rule based logic and other logic toaccomplish the various connection steps, processing steps, comparisonsteps and decision steps.

What is claimed is:
 1. A wall mounted display and sensor unit for abuilding, the wall mounted display and sensor unit comprising: a sensorconfigured to sense an environmental condition; a display; a halo lightemitting diode (LED) system comprising one or more LEDs configured toemit light around at least a portion of an outer edge of the wallmounted display and sensor unit; and a processing circuit configured toreceive one or more data streams, determine whether the one or more datastreams indicate a building emergency condition, and operate the one ormore LEDs of the halo LED system to indicate the building emergencycondition to a user and configured to provide an indication of theenvironmental condition on the display.
 2. The wall mounted display andsensor unit of claim 1, wherein the processing circuit is configured toprovide instructions related to the building emergency condition on thedisplay.
 3. The wall mounted display and sensor unit of claim 1, whereinthe halo LED system further comprises one or more waveguides, whereineach of the one or more waveguides is associated with one of the one ormore LEDs of the halo LED system, wherein each of the one or morewaveguides is configured to transmit the light emitted from one of theone or more LEDs to a halo diffuser, wherein each of the one or morewaveguides is coupled to the halo diffuser at a first end of the one ormore waveguides and is proximate one of the one or more LEDs at a secondend of the one or more waveguides.
 4. The wall mounted display andsensor unit of claim 1, further comprising: an enclosure comprising afront portion and a back portion, wherein a halo diffuser is coupled tothe front portion and the back portion and is located between the frontportion and the back portion.
 5. The wall mounted display and sensorunit of claim 1, wherein the processing circuit is configured to operatethe one or more LEDs of the halo LED system to indicate the buildingemergency condition to the user by operating the one or more LEDs in apattern to indicate one or more emergency response directions to theuser prompting the user to perform a user response to the buildingemergency condition.
 6. The wall mounted display and sensor unit ofclaim 5, wherein operating the one or more LEDs in the pattern toindicate the one or more emergency response directions comprisesactivating the one or more LEDs sequentially to indicate an emergencynavigation direction.
 7. The wall mounted display and sensor unit ofclaim 1, wherein the processing circuit is configured to operate thedisplay to display one or more emergency response directions in responseto a determination that the one or more data streams indicate thebuilding emergency condition.
 8. The wall mounted display and sensorunit of claim 7, wherein the processing circuit is configured togenerate a plurality of navigation directions, each navigation directionassociated with a priority level, prioritize the plurality of navigationdirections, and cause a display screen of the display to display ahighest priority level navigation direction of the plurality ofnavigation directions.
 9. The wall mounted display and sensor unit ofclaim 7, wherein the one or more data streams comprise a building datastream generated by a building management system and a weather datastream generated by a weather server; wherein the wall mounted displayand sensor unit comprises a communication interface configured toreceive the building data stream from the building management system viaa network and the weather data stream from the weather server via thenetwork; wherein the processing circuit is configured to: cause thedisplay to display non-emergency information based on the building datastream; determine whether the weather data stream indicates an emergencyweather condition; and override the display of the non-emergencyinformation by causing a display screen of the display to indicate theone or more emergency response directions in response to a determinationthat the weather data stream indicates the emergency weather condition.10. The wall mounted display and sensor unit of claim 9, wherein the oneor more emergency response directions comprise a building map and one ormore evacuation directions, wherein the one or more evacuationdirections comprise at least one of one or more directions to a buildingexit or one or more directions to an emergency shelter in the building;wherein causing the display to display the one or more emergencyresponse directions comprises causing the display screen to display thebuilding map and the one or more evacuation directions.
 11. The wallmounted display and sensor unit of claim 9, wherein the one or moreemergency response directions comprise an arrow indicating a routethrough the building for the user to follow, wherein causing the displayscreen to display the one or more emergency response directionscomprises causing the display screen to display the arrow.
 12. The wallmounted display and sensor unit of claim 11, wherein the arrow comprisesa first portion and an arrow border surrounding the first portion,wherein the first portion is a first color and the arrow border is asecond color different than the first color.
 13. A display device for abuilding, the display device comprising: a wireless interface; a sensorconfigured to sense an environmental condition; a display; a halo lightemitting diode (LED) system comprising: one or more LEDs configured toemit light; a halo diffuser structured around at least a portion of anouter edge of the display device, wherein the halo diffuser isconfigured to diffuse the emitted light of the one or more LEDs aroundat least the portion of the outer edge of the display device; and aprocessing circuit configured to operate the one or more LEDs of thehalo LED system to indicate a building emergency condition to a user,wherein the building emergency condition is determined using datareceived via the wireless interface, wherein the processing circuitconfigured to provide an indication of the environmental condition onthe display.
 14. The display device of claim 13, wherein the processingcircuit is configured to receive one or more data streams, determinewhether the one or more data streams indicate the building emergencycondition, and operate the one or more LEDs of the halo LED system toindicate the building emergency condition to the user.
 15. The displaydevice of claim 13, wherein the processing circuit is configured todetermine a display device condition that requires user input andoperate the one or more LEDs of the halo LED system to indicate thedisplay device condition to the user.
 16. The display device of claim13, wherein one or more waveguides are coupled to the halo diffuser at afirst end of the one or more waveguides and is proximate to one of theone or more LEDs at a second end of the one or more waveguides.
 17. Thedisplay device of claim 13, wherein the display device comprises anenclosure comprising a front portion and a back portion, wherein thehalo diffuser is coupled to the front portion and the back portion andis located between the front portion and the back portion.
 18. Thedisplay device of claim 13, wherein the processing circuit is configuredto operate the one or more LEDs of the halo LED system to indicate thebuilding emergency condition to the user by operating the one or moreLEDs in a pattern to indicate one or more emergency response directionsto the user prompting the user to perform a user response to thebuilding emergency condition.
 19. The display device of claim 18,wherein operating the one or more LEDs in the pattern to indicate theone or more emergency response directions comprises activating the oneor more LEDs sequentially to indicate an emergency navigation direction.20. A controller for a building, the controller comprising: a halo lightsystem comprising one or more lighting components configured to emitlight and a halo diffuser structured around at least a portion of anouter edge of the controller, wherein the halo diffuser is configured todiffuse the emitted light of the one or more lighting components aroundat least the portion of the outer edge of the controller; a displaydevice configured to display information to a user; and a processingcircuit configured to receive one or more data streams, determinewhether at least one of the one or more data streams indicate an alarmcondition, operate the one or more lighting components of the halo lightsystem to indicate the alarm condition to the user, and operate thedisplay device to display the alarm condition to the user.